Who is Dynamics 365 implementation for?
FlitStack AI’s Dynamics 365 implementation is for teams moving onto Microsoft Dynamics 365 Sales from another CRM, usually because the business already runs on Microsoft 365 and wants the CRM inside the same ecosystem. The project ends with your data in Dataverse and Dynamics set up for how you sell.
Common starting points:
- Salesforce to Dynamics 365, where Account Contact Relations and record types need a plan. See Salesforce to Dynamics 365.
- HubSpot to Dynamics 365, where HubSpot companies become accounts and lifecycle stages become the lead-to-opportunity path. See HubSpot to Dynamics 365.
- Zoho CRM or Odoo to Dynamics 365, often part of a wider Microsoft move. See Zoho CRM to Dynamics 365 and Odoo to Dynamics 365.
- Zendesk Sell to Dynamics 365, a forced move before Sell’s retirement. See Zendesk Sell to Dynamics 365.
What does Microsoft offer natively, and where does it stop?
| Microsoft option | What it does | Where it stops |
|---|---|---|
| Import from Excel, CSV or XML | Imports records into Dynamics 365 Sales from a file | 8 MB per file (32 MB for .zip), one file at a time |
| Import Data Wizard | Maps file columns to tables, including notes and attachments | Microsoft recommends 20,000 rows or fewer per import and a programmatic route for large volumes |
| Record Created On (overriddencreatedon) | Lets an import keep the source created date | Needs a specific privilege; Created By and Modified On can’t be imported |
| Configuration Migration tool | Moves configuration data between environments | Built for configuration, not for end-user records like accounts and contacts from another vendor |
| FastTrack for Dynamics 365 | An onboarding programme from Microsoft’s engineering team with best practices and expert advice | Eligibility depends on licence spend and a qualified partner; Microsoft doesn’t design or develop the solution |
Microsoft points customers to its partner directory for implementation work.
What does FlitStack AI add?
An API migration, not a file import. We extract from your source through its API and load Dataverse in dependency order. That avoids the file-size and row limits, and lookups between accounts, contacts, opportunities and activities resolve as they load.
History with its real dates. Source created dates go into Record Created On, and activities land on the right records with their original timestamps. Values Dataverse won’t let you set, such as the original creator, are kept in their own columns.
Checks you can sign off. A sample run before production, a hash on every record at both ends, and one-click rollback if the production run fails validation.
What usually goes wrong in a Dynamics 365 migration?
- Picklists that become choices. Every source picklist value needs a matching Dataverse choice value, created before the load.
- GUID ordering. Dataverse links records by GUID, so parents must exist before children. We load in strict dependency order.
- Many-to-many relationships. A contact linked to several accounts in the source needs a primary account in Dynamics plus connection records for the rest.
- Security roles at go-live. Users without the right role see nothing on day one. Roles are tested in the sample phase.
What does the Dynamics 365 setup cover?
- Dataverse model: tables, columns, choices, forms and views.
- Sales process: opportunity stages and business process flows.
- Automation: Power Automate flows rebuilt from your source automations.
- Access: business units, teams and security roles.
- Integrations with Outlook, Teams, forms and the tools around Dynamics.
Training is an optional add-on.
Should the sample run go into a sandbox environment?
Yes, where you have one. A sandbox environment lets your team check migrated records, test business process flows and Power Automate flows against real data, and try security roles before production. When the design is signed off, the same mapping runs against production, so what you tested is what you get.
Do you work with Microsoft partners?
Often. Larger Dynamics programmes usually have a Microsoft partner for licensing, FastTrack or finance and operations work. FlitStack AI can take the CRM data migration and the Dynamics 365 Sales setup as a defined workstream, with handover points agreed on the scoping call.
How is it priced?
Each Dynamics 365 implementation gets a fixed quote after a free scoping call. Record count, custom tables, data complexity, the amount of process work and your cutover window move the number. See how pricing works.
Where does FlitStack AI fit?
If you have a Microsoft partner for the wider programme, we can own the CRM migration and setup alongside them. If you want the whole move handled, with history intact and a validation report before cutover, book a scoping call. You’ll have a written quote within one business day.

