Available for: Starter, Business, Education, and Enterprise plans
Import your content from Freehand into Miro to leverage a variety of features tailored to your collaborative needs.
⚠️ Editing imported content is one-way. Changes made in Miro will not sync back to Freehand.
✏️ Freehand boards under Free or Restricted licenses can be migrated.
Import from Freehand to Miro
- Access the Freehand board you wish to export to Miro.
- Download the file in .RTB, Miro's proprietary format, directly from Freehand. Navigate to the Tools menu and select Export to Miro board. The file will be saved to your default download folder. Freehand will notify you once the download is complete.
- Open your Miro dashboard.
- On the top-right area of the Miro dashboard, click the + Create new button, click Import, and then click Import from Freehand.
- Choose the previously downloaded .RTB file from your system.
- All content is now imported into a new Miro board in an editable format.
- While most content will seamlessly transition, minor adjustments may be necessary due to variations in styling and formatting options between Freehand and Miro. Refer to How Freehand objects appear in Miro for guidance.
Bulk import from Freehand to Miro
✏️ - The Freehand token is valid only for two weeks from the date you received the token.
- From December 31, 2024, at 11:59 PM EST onwards, Freehand and all associated migration tokens will be discontinued and invalidated. Users will no longer be able to generate new tokens or access Freehand.
Best practices and considerations
How Freehand objects appear in Miro
This table provides a comprehensive comparison of objects between Freehand and Miro.
| Freehand | Miro | Touchups needed |
| Boards | Kanban | None |
| Cards | Cards |
Jira cards in Freehand will be imported as Jira cards in Miro. However, they will not be connected to the existing instance as users will need to re-authenticate their Jira accounts in Miro. ADO, Trello, Asana cards are not supported. |
| Collaborators and sharing | Can be recreated manually | None |
| Comments | Can be recreated manually | None |
| Connectors/Lines | Connectors/Lines | None |
| Drawings/Diagrams/Shapes | Shapes, Text and Connectors | None |
| Dynamic data tables | CSV | Content can be downloaded and edited as a .CSV file from the Miro board. |
|
Embeds: Google and Microsoft Docs, YouTube, Spotify, Loom |
Name of the source (e.g. Google, YouTube) and the URL for the embed | If users wish to re-embed a document they can Upload via URL. |
| Emoji reactions | Can be recreated manually | None |
| Frames | Frames | None |
| Grids (tables) | Tables | None |
| Grouped objects | Ungrouped objects | To regroup objects, select all relevant objects and press Cmd/Ctrl + G, or click Group objects from the context menu. |
| Images | Images | None |
| Pages | Embedded doc | Content can be downloaded and edited as a .docx file from the Miro board. |
| Prototypes | Name of the source (InVision) and the URL for the embed | If users wish to re-embed a document they can Upload via URL to re-embed. |
|
Smart widgets: Flip card, Poll, This or That, Charts, Counter, Leaderboard, Spinner, Buzzer, People, Story Points, T-Shirt Size, Timer, Action Buttons |
PNG of the smart widget at time of import is created | Content is not editable. |
| Sticky notes | Sticky notes | Font sizes of text within sticky notes may need to be adjusted. |
| Timeline (Gantt) | CSV | Content can be downloaded and edited as a .CSV file from the Miro board. |
|
Wireframes |
Wireframes |
Some objects may need to be redrawn. |
Limitations
While Freehand and Miro offer similar functionalities, some differences may exist:
- Miro Text boxes can accommodate up to 6,000 characters, including spaces. Any additional text will be cropped.
- Miro Sticky notes do not support color palette adjustments, or text bulleting.
- Freehand Smart widgets are imported as static images and are not editable.
- Comments, emojis, and prototypes are not migrated.
- The Freehand token is valid only for two weeks from the date you received the token.
-
From December 31, 2024, at 11:59 PM EST onwards, Freehand and all associated migration tokens will be discontinued and invalidated. Users will no longer be able to generate new tokens or access Freehand.
Compare organizational structure between Freehand and Miro
It is important to establish a baseline understanding of how the organizational structures differ between Freehand and Miro for more efficient migration.
Freehand organizational layers
- Teams: Each subdomain you have access to in InVision is considered a Team. If you only have access to one subdomain, you have one team.
- Groups: Document folders that aid in grouping and sharing documents across your team.
- Spaces: An additional layer of organization within groups for your documents.
✏️ If your team utilized the Space overview capability, you will need to manually migrate this content from Freehand to Miro. We recommend copying Space overview content to a Miro board.
Miro organizational layers
- Organizations: You typically only have access to a single organization.
- Teams: Shared workspaces where users collaborate on boards and projects.
- Projects: Collections of boards within a team, facilitating organization, retrieval, and sharing of boards.
Consider your InVision Groups to be equivalent to Miro Projects. For each group you plan to migrate from InVision, we recommend creating a Miro project with the same name. For example, if you had a InVision group named "Acme Corp Relaunch Project," we suggest setting up a Miro project with the identical name, "Acme Corp Relaunch Project."
💡 For further questions around Freehand migration, please contact Miro Support or reach out to your Miro Customer Success Manager directly.