Skip to content
Get a quote

Dynamics 365 implementation and data migration

In short

FlitStack AI implements Microsoft Dynamics 365 Sales as one project: it migrates accounts, contacts, leads, opportunities, activities, notes and attachments from your old CRM with original created dates, field-level validation and one-click rollback, then sets up tables, columns, business process flows, Power Automate flows and security roles.

By

From Your data and process
DestinationDynamics 365
Data migrationPipelinesPropertiesAutomationPermissions
Implementation and migration · one engagement

What's included

  • CRM data migration into Dynamics 365 Sales. Accounts, contacts, leads, opportunities, phone calls, emails, appointments, tasks, notes, attachments, custom columns and custom tables, loaded in dependency order with lookups resolved.
  • Original created dates and owners. Source created dates written to Dataverse's Record Created On field during the migration; owners matched to Dynamics users by email.
  • Tables, columns and forms. Custom tables, columns, choices (option sets), forms and views set up in Dataverse before data lands.
  • Sales process and automation. Opportunity stages, business process flows and Power Automate flows rebuilt from your source automations.
  • Security roles and business units. Users, teams, business units and security roles configured so each team sees the right records.
  • Integrations. Outlook and Teams, forms and the systems around Dynamics connected through native features or Microsoft Marketplace apps, scoped in the quote.
  • Training and onboarding (optional add-on). Admin handover and role-based sessions for sellers and managers, added only if you want them.

Not included

  • Plug-ins, custom code or PCF controls
  • Dynamics 365 finance and operations apps or Business Central, unless scoped separately
  • Licence purchase or Microsoft agreement changes

How the engagement runs

  1. Scoping call

    A free call with a migration engineer on your source CRM, record counts, custom tables and the Dynamics processes you need. A written quote follows within one business day.

  2. Audit and Dataverse design

    Source data profile and schema discovery, then a mapping plan and a Dynamics design: tables, columns, choices, the lead-to-opportunity path, flows and security roles.

  3. Build the environment

    Tables, columns, choices, users and security roles created before any production data arrives, ideally in a sandbox environment first.

  4. Sample migration

    A representative subset with its activities and attachments. You review it in Dynamics, and a hash-based diff shows anything that didn't round-trip.

  5. Full migration and cutover

    Production run in dependency order (accounts, contacts and leads, opportunities, then activities), a delta sync for changes during cutover, then flows switched on.

  6. Handover and support

    Validation report, build documentation and a direct line to a migration engineer for 14 days after cutover.

FlitStack AI, an agency, or the platform's own onboarding?

CriterionFlitStack AITypical agencyPlatform's own offer
Hands-on data migrationIncluded, run by engineers on FlitStack AI's migration platformUsually included by Microsoft partners, often with their own tools or scriptsImport from Excel or CSV and the Import Data Wizard are self-serve; Microsoft points larger moves to partners
History and created datesActivities, notes and attachments with source created dates in Record Created OnPossible, depends on the partner's toolingSupported through the Record Created On field if you build the import yourself
Process setupTables, business process flows, Power Automate flows and security roles in the same projectA core strength, often with wider Power Platform and ERP workFastTrack gives eligible customers guidance and best practice, but doesn't design or build the solution
Validation and rollbackSample run, field-level validation report and one-click rollbackVaries by partnerImport job logs with failed rows; rollback is up to you
CutoverDelta sync for records changed during the projectVaries; often a data freezeUsually a data freeze
Pricing modelFixed project quote after scopingDay rates or a statement of workImport tools included; FastTrack has spend-based eligibility

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:

What does Microsoft offer natively, and where does it stop?

Microsoft optionWhat it doesWhere it stops
Import from Excel, CSV or XMLImports records into Dynamics 365 Sales from a file8 MB per file (32 MB for .zip), one file at a time
Import Data WizardMaps file columns to tables, including notes and attachmentsMicrosoft 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 dateNeeds a specific privilege; Created By and Modified On can’t be imported
Configuration Migration toolMoves configuration data between environmentsBuilt for configuration, not for end-user records like accounts and contacts from another vendor
FastTrack for Dynamics 365An onboarding programme from Microsoft’s engineering team with best practices and expert adviceEligibility 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?

  1. Dataverse model: tables, columns, choices, forms and views.
  2. Sales process: opportunity stages and business process flows.
  3. Automation: Power Automate flows rebuilt from your source automations.
  4. Access: business units, teams and security roles.
  5. 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.

Questions, answered

A few useful answers.

Is FlitStack AI a Dynamics 365 implementation partner?

FlitStack AI implements Dynamics 365 Sales for its customers: data migration, Dataverse design, sales process, flows and security roles. If your project also needs a Microsoft Solutions Partner (for FastTrack eligibility or finance and operations work), we can run the CRM migration alongside them.

Can we use FastTrack instead?

FastTrack is Microsoft's onboarding programme for eligible customers. It offers best practices, tools and expert advice, but Microsoft says it has no formal role on the project and doesn't design or develop the solution. Someone still has to do the migration and build.

Can't we use the Import Data Wizard?

For small, clean files, yes. Microsoft recommends keeping wizard imports to 20,000 rows or fewer and using a programmatic route for large volumes. FlitStack AI uses the API, resolves lookups across tables, and checks every record after the load.

Can we keep the original created dates?

Yes. Dataverse lets an import write the source date to Record Created On, which needs the right privilege. Created By and Modified On can't be imported, so we keep source values for those in their own columns.

How long does a Dynamics 365 implementation take?

The data run for most CRM migrations under 1M records takes 48–72 hours, and custom-table-heavy ones take 5–7 days. Business process flows, Power Automate flows and integrations add time based on scope, and the quote states the full timeline.

Get a quote

Talk to us about Dynamics 365.

Tell us what you're moving and what the new system needs to do. We scope the data and the setup with you, then send a quote.

Get a quote