CompareIQ
TestIQ
MigrateIQ
Sales Order Agent
Processed only for your migrations
Migrated data is used only to carry out the migrations you start.
Coming soon · Data migration for Dynamics 365
Move data between Dynamics 365 environments in a repeatable order.
Register environments, copy data between environments and companies, load files and run sequence templates, with every migration tracked by its own request number and results.
Four ways to move data. One repeatable order.
Register the environments once, then copy, load or sequence data between them, level by level.
Register and manage environments
Every source and target, registered once.
Register the Dynamics 365 environments and companies you migrate between, and mark which of them are production. Only environments you have registered can be used as a source or a target.
- Development, Test, UAT and Production
- Companies within each environment
- Production clearly identified
Registered environments
- Development → Test → UAT → Production
- Only registered environments can be a source or a target
In practice
Four steps to a migration.
Each one tracked by its own request number.
- 01
Register environments
Add the source and target environments and companies.
- 02
Choose the scope
Pick the data, upload files, and review the loading order.
- 03
Start the migration
Levels load in order, with stop on error.
- 04
Review results
Check created, updated and rejected counts per item.
MigrateIQ at a glance
Who it is for
- Data migration teams
- Functional consultants
- Technical consultants
- Implementation programmes
- Application support teams
What each migration reports
- Succeeded
- Partially succeeded
- Failed, with the message shown
- Not run, after an earlier failure
When to use it
- Initial data loads
- Moving data between environments
- Rolling out a new company
- Cut-over and go-live loads
Your data
Your data stays yours.
Registered environments only
Data moves only between environments you have registered and authorised.
Access kept to what is needed
Access to your environments is limited to the migrations you start.
Files kept only as long as needed
Uploaded files are retained only to carry out and report on a migration.
Frequently asked questions
Quick answers on scope, fit and how we work. Anything else, ask us directly.
Talk to a specialistA short call to walk through your situation and the right next step.
MigrateIQ is coming soon. Contact us to ask about availability and early access.
The migration ran to completion but some records or data items were rejected, most often because a required value was missing or a referenced record did not exist in the target. The per-item results show the counts and the destination system's own message for each one.
When stop on error is enabled, a failure in one level prevents later levels from loading, so data is never created on top of data that is missing. Fix the cause in the failed level and start a new migration.
No. A migration creates and updates records in the target environment and cannot be assumed to be reversible. Confirm the target environment and company, and take your own backups, before starting.
You do. You keep ownership of the data you migrate, the files you upload, and the mappings and sequence templates you create.