Migration software
Apps4.Pro
Suggested in 5 of our migration playbooks, mainly for Microsoft 365 and Business apps. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What it handles
The limits of the built-in tools that Apps4.Pro gets around, as covered in our playbooks.
Microsoft 365 tenant-to-tenant migration
- Set expectations on what users loseMigrates Microsoft Forms with their responses and attachments to the target tenant. Responses show as posted by the service account, and there is no incremental pass.
- Microsoft's built-in tools do not move Teams channel conversations, Planner or Forms.Migrates Microsoft Forms with responses. Responses show as posted by the service account.
Microsoft Forms migration to another tenant or owner
- Export responses before anyone deletes accountsDiscovers forms after users and groups are mapped, and supports bulk migration from a CSV. Source and target users need a Forms-enabled licence, so keep source accounts licensed until the run is complete.
- Use the offline copy, not the live workbook, as your recordMigrates user and group forms with their responses, attachments and collaborators. Responses appear as posted by the service account, group-level permissions are not migrated, and there is no incremental pass.
- Microsoft deletes a user's Forms data 30 days after the account is deleted. Once the account is permanently (hard) deleted, its forms cannot be recovered.Discovers all user and group forms after users and groups are mapped, and flags forms whose owner has no Forms licence. Keep source accounts licensed until the run is complete.
- Duplicate link: responses never move with the copy.Migrates forms with their responses. Responses show as posted by the service account, group permissions are not migrated, and there is no incremental pass.
Power BI tenant-to-tenant migration
- Retire content with no viewersMigrates workspaces, reports, datasets, dashboards with tile positions and refresh schedules. Apps, dataflows, paginated reports and link-based permissions are not migrated, and gateways must be set up by hand.
- Download and republish: every report you keep is downloaded, republished and set up again by hand.Migrates workspaces, reports, datasets, dashboards and refresh schedules. Apps, dataflows, paginated reports and link-based permissions are not migrated, and gateways are set up by hand.
Power Apps and Power Automate tenant-to-tenant migration
- The default environment cannot use the environment moveMigrates cloud flows tenant to tenant with environment, user and creator mapping, auto-maps SharePoint site URLs and lists, and keeps each flow on or off. Run history, desktop flows and environment creation are not migrated, and users fix connections in the target.
- Environment move: default, developer, trial and Teams environments cannot use it.Migrates cloud flows between tenants with environment and user mapping. Run history and desktop flows are not migrated, and users fix connections in the target.
Trello or Asana to Microsoft Planner migration guide
- Decide what you are not moving: comments, attachments and historyMoves Trello cards with comments, attachments, checklists, labels and due dates into Planner tasks.
- Map people by email, not by nameMaps Trello board members to Planner plan members, and Trello labels to Planner labels.
- Planner assigns tasks to Microsoft 365 accounts, so names that match two people or guests with no account end up unassigned.Maps Trello board members to Planner plan members, and Trello labels to Planner labels.
- By hand, flow or script: comments, attachments and history do not move. Trello's CSV has no comments, and the board JSON holds only the latest 1,000 actions.Moves Trello cards with comments, attachments, checklists, labels and due dates into Planner tasks.
How it handles key settings
From the settings checklists in our playbooks: what Apps4.Pro carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Microsoft 365 groups, Planner and Forms | Migrates forms with their responses, shown as posted by the service account. There is no top-up pass. | Microsoft 365 tenant-to-tenant migration |
| What a duplicate link copies | Migrates question settings (required, subtitles, restrictions, branching), themes, response settings and receipt options. | Microsoft Forms migration to another tenant or owner |
| Responses | Migrates responses, but they show as posted by the tool's service account. Whether original names and dates are kept: not stated in Apps4.Pro's documentation: test it in your pilot. | Microsoft Forms migration to another tenant or owner |
| Who can respond | Migrates the response collection and response options settings. | Microsoft Forms migration to another tenant or owner |
| File upload questions | Personal forms with upload questions are migrated as group forms, with uploaded files in the group's SharePoint. After migration you cannot add collaborators or new upload questions to those forms. | Microsoft Forms migration to another tenant or owner |
| Owners and form limits | For group forms, both of the tool's connector accounts must be members of the group. | Microsoft Forms migration to another tenant or owner |
| Departed owners and account deletion | Source and target users need a Forms-enabled licence, and its scan flags forms whose owner has none. Keep source accounts licensed until the run is complete. | Microsoft Forms migration to another tenant or owner |
| Published links, QR codes and embeds | Its summary report lists source and target form addresses. Whether old links redirect: not stated in Apps4.Pro's documentation: test it in your pilot. | Microsoft Forms migration to another tenant or owner |
| Power Automate flows and response workbooks | Flows: not stated in Apps4.Pro's documentation: test it in your pilot. | Microsoft Forms migration to another tenant or owner |
| Collaborators and group permissions | Migrates collaborator permissions. Group-level permissions are not migrated. | Microsoft Forms migration to another tenant or owner |
| Responses during the change | Incremental migration (a top-up copy of only what changed) is not supported. | Microsoft Forms migration to another tenant or owner |
| What can be downloaded as a .pbix | Migrates reports and datasets, linked and unlinked. Models using the large semantic model storage format are not migrated. | Power BI tenant-to-tenant migration |
| Data inside the models | Lists on-premises data as not migrated. | Power BI tenant-to-tenant migration |
| Shared semantic models and live-connected reports | Reports built in the Power BI service on a shared dataset are listed as not migrated. | Power BI tenant-to-tenant migration |
| Workspace roles and sharing | Migrates direct-access permissions on workspaces, reports, datasets and dashboards. Link-based sharing is not migrated. | Power BI tenant-to-tenant migration |
| Row-level security members | Row-level security members: not stated in Apps4.Pro's documentation: test it in your pilot. | Power BI tenant-to-tenant migration |
| Gateways and data source credentials | Migrates data source credentials as dataset settings. Gateways must be set up by hand. | Power BI tenant-to-tenant migration |
| Scheduled refresh | Migrates refresh schedules, including frequency, time zone and failure notifications. | Power BI tenant-to-tenant migration |
| Dashboards, apps, subscriptions and alerts | Migrates dashboards with their tiles and tile positions. Apps are not migrated. | Power BI tenant-to-tenant migration |
| Dataflows, paginated reports and other items | Dataflows, apps, paginated reports, scorecards and streaming datasets are not migrated. | Power BI tenant-to-tenant migration |
| Licences and capacity for viewers | The tool's connector accounts need a Power BI licence and the Fabric Administrator role in both tenants. | Power BI tenant-to-tenant migration |
| Changes made during the migration | Supports incremental migration (a top-up copy of only what changed) for dashboards, datasets, reports, tiles, settings and permissions. | Power BI tenant-to-tenant migration |
| Which environments can use the environment move | Migrates cloud flows between tenants with environment and user mapping. | Power Apps and Power Automate tenant-to-tenant migration |
| Connections, custom connectors and gateways | Users sign in to its End User Portal to set up connections again and restore each flow. | Power Apps and Power Automate tenant-to-tenant migration |
| User mapping | Maps flow creators and owners to target users. | Power Apps and Power Automate tenant-to-tenant migration |
| Flow state and run history | Migrates each flow's on or off state. Run history and desktop flows are not migrated. | Power Apps and Power Automate tenant-to-tenant migration |
| HTTP triggers and other trigger addresses | Its inventory does not include trigger and action details. How triggers are repointed: not stated in Apps4.Pro's documentation: test it in your pilot. | Power Apps and Power Automate tenant-to-tenant migration |
| Comments | Migrates comments. Whether the original author and date are kept: not stated in Apps4.Pro's documentation: test it in your pilot. | Trello or Asana to Microsoft Planner migration guide |
| Attachments | Moves card attachments (files) into Planner tasks. | Trello or Asana to Microsoft Planner migration guide |
| Checklists and subtasks | Says checklists are preserved. | Trello or Asana to Microsoft Planner migration guide |
| Labels and tags | Maps Trello labels to Planner labels. | Trello or Asana to Microsoft Planner migration guide |
| Assignees and members | Maps Trello board members to Planner plan members. | Trello or Asana to Microsoft Planner migration guide |
| Created dates, completed tasks and who did what | Not stated in Apps4.Pro's documentation: test it in your pilot. | Trello or Asana to Microsoft Planner migration guide |
| Archived cards and finished tasks | Lets you include or exclude archived cards, and mark them completed in Planner. | Trello or Asana to Microsoft Planner migration guide |
| Basic or premium plan | Premium plans: not stated on this tool's page (Apps4.Pro has a separate premium migration page): check with Apps4.Pro. | Trello or Asana to Microsoft Planner migration guide |
| Running an import again | Incremental runs: not stated in Apps4.Pro's documentation: test it in your pilot. | Trello or Asana to Microsoft Planner migration guide |
Tools for the same jobs
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.