How to prepare your company for a migration to Dynamics 365: An essential guide

A migration to Dynamics 365 is one of the most impactful decisions a Canadian SMB can make — but also one of the most disruptive if handled without a plan. Done well, it gives your team a unified cloud platform for ERP and CRM, with built-in Microsoft Copilot AI, automatic updates, and the scalability to grow without re-implementing every three years. Done poorly, it leads to lost data, user resistance, budget overruns, and months of cleanup.

At Gestisoft, we've guided hundreds of Canadian organizations through this process — from companies leaving legacy systems like Dynamics NAV, Dynamics GP, or Salesforce, to organizations doing a first-ever CRM or ERP implementation. This guide distills that experience into a practical, step-by-step framework you can start using today.

Quick answer: A successful migration to Dynamics 365 requires eight preparation phases: stakeholder alignment, platform selection, user readiness, data audit, data mapping, system configuration, testing, and go-live scheduling. Each phase builds on the last — skipping one almost always creates problems downstream.

Why a Migration to Dynamics 365 Requires More Than a Data Transfer

Many companies underestimate what switching to Dynamics 365 actually involves. It is not simply exporting your old data and importing it into a new system. You're changing workflows, user habits, integrations, and the underlying architecture of how your business captures and uses information.

• A poorly planned move can lead to:
• Corrupted or incomplete records that take months to reconcile
• Users reverting to spreadsheets because they weren't trained on the new system
• Integrations with other tools (invoicing, payroll, e-commerce) that break on go-live day
• Budget overruns from unplanned customizations discovered mid-project

According to Microsoft's Forrester Total Economic Impact study (June 2024), a mid-sized organization that completed a migration to Dynamics 365 Business Central saw up to 18% productivity gains in finance and operations — but those gains were tied directly to proper planning and change management, not just the technology itself.

In Canada, there's also an added urgency: Microsoft officially ended new perpetual licenses for Dynamics GP on April 1, 2025, and is ending GP subscription licenses on April 1, 2026. Organizations still on Dynamics NAV or GP face real end-of-support timelines that make planning a migration to Dynamics 365 a now-or-never conversation.

Step 1: Align Stakeholders and Define Your Goals

Before touching a single database or contacting a vendor, your project needs internal alignment. This is the phase most companies rush — and the one that causes the most downstream problems.

Start by bringing together the people who will be most affected: your operations, finance, IT, and sales leads. Work with your Microsoft Dynamics 365 consultant to agree on:

• Why are you migrating? Is it a forced upgrade (GP end-of-life), a desire for cloud capabilities, a Copilot AI initiative, or a need for better reporting?
• What does success look like? Define measurable outcomes — a 30% reduction in manual data entry, a full close cycle completed in three days instead of seven, etc.
• What is your timeline and budget? Be realistic. A typical SMB migration to Dynamics 365 takes 3–6 months for a standard implementation, longer for complex customizations.
• Who owns the project? Name a project lead who has the authority to make decisions and keep stakeholders accountable.

Documenting this in a one-page project charter prevents scope creep and keeps everyone grounded when things get complicated. Gestisoft's analysis service is specifically designed to help you build this foundation before committing to a full implementation scope.

Step 2: Choose the Right Dynamics 365 Platform and Modules

Dynamics 365 is not a single product — it's a suite of modular applications. Choosing the right combination upfront is critical because the modules you select will shape your data model, your integration requirements, and your total cost.

The two main tracks for Canadian SMBs planning a migration to Dynamics 365 are:

Dynamics 365 Business Central (ERP) — Best for companies that need to manage financials, inventory, manufacturing, supply chain, and operations in a single platform. This is the recommended upgrade path for organizations currently on Dynamics GP or Dynamics NAV. Business Central is at the heart of ERP in digital transformation for Canadian SMBs.

Dynamics 365 Customer Engagement / Sales (CRM) — Best for organizations focused on managing sales pipelines, customer service, field service, or marketing automation. This is the recommended path for companies leaving Salesforce, older Dynamics CRM versions, or spreadsheet-based sales tracking.

Some organizations will need both. A manufacturing company that wants a unified view of inventory and customer orders can connect Business Central and Dynamics 365 Sales natively via Microsoft's Power Platform.

When evaluating which modules to activate, ask:

• Which business processes are currently the most painful or manual?
• Are there regulatory compliance requirements specific to our industry or province (e.g., Quebec's Loi 25 data residency obligations)?
• What third-party integrations must be preserved (payroll, e-commerce, logistics)?
• Where does Microsoft Copilot add the most value for our team's day-to-day work?

Not sure which product is right for your needs? Our guide on what is ERP consulting walks through how a certified partner structures that evaluation.

Step 3: Prepare Your Team for Change

User adoption is the number one reason a migration to Dynamics 365 succeeds or fails after go-live. A technically perfect implementation will still fail if your people don't trust the new system, don't know how to use it, or weren't involved in the decision to switch.

Start user preparation as early as Step 2 — not after the system is configured. Here's what that looks like in practice:

Communicate early and honestly. Tell your team why you're moving to Dynamics 365, what's changing, and what's not. Address the fear that automation might threaten jobs or that the new system will make their work harder.

Identify champions in each department. Find one person per team who is tech-comfortable and willing to learn the new system first. These internal champions become your go-live support network and reduce the volume of help desk requests in the first weeks.

Plan structured training, not just documentation. A 30-minute video library is not the same as hands-on, role-specific training. Work with your Dynamics 365 implementation partner to build training that mirrors your actual workflows — not a generic walkthrough of every menu.

Set expectations for the adjustment period. Even the best go-lives have a 2–4 week productivity dip as users get comfortable. Build this into your timeline so it doesn't create panic.

Step 4: Audit and Clean Your Data Before the Move

Data quality is the most underestimated variable in any migration to Dynamics 365. Organizations often assume their current data is clean — and are surprised to discover thousands of duplicate records, broken relationships, empty required fields, and outdated customer information.

Importing bad data into Dynamics 365 Business Central or Dynamics 365 CRM doesn't fix those problems. It brings them into a new system where they're harder to find and more expensive to fix.

A proper data audit before your move should cover:

• Deduplication — Identify and merge duplicate customer, vendor, and contact records
• Completeness — Identify records with missing required fields (addresses, tax numbers, contact info)
• Relevance — Decide which historical data is worth migrating vs. archiving. Do you need 10 years of closed orders in the live system, or is 2–3 years sufficient?
• Data ownership — Assign someone in your team to be accountable for data quality going forward. Projects without a data governance policy tend to degrade back to the same state within 18 months
• Quebec-specific compliance — If your organization is subject to Quebec's Loi 25, verify that personal data complies with consent and storage requirements before moving it to a cloud environment

This is also the right moment to define your data governance rules for the new system: how are records created, who can edit them, what's the standard for a "complete" account, and how often will data be reviewed?

Step 5: Map Your Data to the New System

Once your data is clean, you need to understand how it maps to the Dynamics 365 data model. This step is often done in parallel with system configuration (Step 6) because the two are tightly connected.

Data mapping means documenting:

• Where each field in your current system maps to in Dynamics 365 (e.g., "Customer No." in your old CRM → "Account Number" in Dynamics 365 Sales)
• Which fields don't have a direct equivalent and need custom fields or transformations
• Which legacy modules or data categories have no equivalent in Dynamics 365 and need to be handled separately (archived, migrated to a custom table, or dropped)
• How data relationships (e.g., a customer linked to multiple contacts and multiple open orders) will be preserved during the cutover

Microsoft provides native tools for several source systems:

• Dynamics GP → Business Central: Built-in GP migration extension in Business Central
• Dynamics NAV → Business Central: Supported upgrade paths for NAV 2015 and later — see our detailed guide on challenges in migrating from Dynamics NAV to Dynamics 365 Business Central
• Dynamics CRM (on-premises) → Dynamics 365 Sales: Microsoft's OP2OL (On-Premises to Online) service

For non-Microsoft source systems (Salesforce, SAP, or spreadsheets), third-party tools like KingswaySoft's SSIS Integration Toolkit are commonly used by certified partners to support a migration to Dynamics 365.

Step 6: Configure the New System with Migration in Mind

A common mistake is treating system configuration and data migration as two separate workstreams handled by two separate teams. In practice, they must run in parallel — because how you configure the system determines where the data needs to land.

If you decide during configuration to rename a field, change a lookup table, or create a new required field, those decisions immediately affect your data mapping from Step 5. Any configuration change made after mapping is finalized forces a remapping exercise.

The most effective approach is to have the same team handle both streams simultaneously. At Gestisoft, our migration service combines data transfer and system configuration into a single integrated workstream to avoid exactly this problem.

Key configuration decisions that affect every migration to Dynamics 365:

• Chart of accounts structure (for Business Central / ERP projects)
• Custom fields and entities required to preserve data from your legacy system
• Security roles and access levels (who sees what after go-live)
• Integration settings for connected tools (Outlook, Teams, payroll, e-commerce) via Power Platform
• Microsoft Copilot configuration — learn how to automate repetitive tasks with Copilot in Dynamics 365 from day one

Step 7: Test Everything Before Go-Live

Testing is not optional — it's the safety net that prevents a go-live disaster. Yet many projects cut testing short due to time pressure, only to discover critical issues in production.

A proper testing plan for a migration to Dynamics 365 includes:

Data validation testing — Verify that the migrated data is complete, accurate, and correctly related. Run record counts before and after. Spot-check 10–20% of records manually across key tables (customers, vendors, transactions, contacts).

Functional testing — Walk through your critical business processes end-to-end in the new system: create a sales order, process an invoice, run a financial report, close a service ticket. Confirm that every workflow your team depends on actually works.

Integration testing — Test all connected systems (payroll, e-commerce, logistics, Teams) to confirm they still function correctly against the new Dynamics 365 environment.

User acceptance testing (UAT) — Have real end users from each department run through their actual day-to-day tasks in the test environment. Collect their feedback formally and resolve issues before go-live.

Copilot and AI feature testing — If you're activating Microsoft Copilot for Finance or other AI features, test them in your specific data context. Generic AI features sometimes behave unexpectedly with custom data models.

Aim to complete at least one full test cycle with a representative data sample (typically 20–30% of production data) before executing the final go-live cutover.

Step 8: Schedule and Execute the Go-Live

With preparation complete, data clean, the system configured, and testing signed off, you're ready to schedule the go-live for your migration to Dynamics 365.

Key go-live decisions:

Pick a low-volume window. Schedule go-live during a period of lower business activity — not at month-end, quarter-end, or during your busiest sales period. For most Canadian businesses, late summer or early January tend to be lower-risk windows.

Define your cutover plan. At what point does the old system stop accepting new entries? How long is the overlap period where both systems are accessible? Who is authorized to enter data into the new system from day one?

Plan for a data freeze. In the days immediately before go-live, freeze data entry in the old system (or at minimum, track everything entered manually so it can be re-entered after cutover).

Have a rollback plan. Define the conditions under which you would delay or reverse go-live, and who has the authority to make that call. Having a rollback plan doesn't mean you expect to use it — it means you've thought through the worst case.

Communicate the go-live date broadly. Every person in your organization who touches the system should know the date, what to expect in the first week, and who to contact for support.

After go-live, plan for 2–4 weeks of hypercare: intensive support from your implementation partner, daily check-ins with department leads, and rapid resolution of issues as they surface.

The Canadian Context: What Makes a Migration to Dynamics 365 Different Here

Canadian companies — and Quebec businesses in particular — face a few specific considerations that generic migration guides don't cover:

Bilingual data management. If your customer base is bilingual, your Dynamics 365 environment needs to support both English and French field values, labels, and reports. Business Central and Dynamics 365 both support multilingual configurations, but this needs to be scoped during Step 2, not discovered at go-live.

Quebec Loi 25 compliance. Quebec's privacy law (in effect since 2023) imposes strict requirements on how personal information is stored, processed, and transferred — including in cloud systems. Before moving personal data to Dynamics 365's Azure cloud environment, confirm your organization's compliance posture with a legal or privacy advisor.

Microsoft GP and NAV end-of-life timelines. If you're on Dynamics GP, Microsoft has set a firm timeline: new perpetual licenses ended April 1, 2025, and subscription licenses end April 1, 2026. Extended support runs to 2031, but the window for a managed, unhurried migration to Dynamics 365 is narrowing. Organizations on NAV should similarly be planning their Business Central upgrade now.

Microsoft Partner support in Canada. Working with a Canadian-certified Microsoft Partner like Gestisoft means your team understands local tax regulations, payroll requirements, and CRA compliance — factors that directly affect how your Business Central chart of accounts and reporting must be configured.

Explore More

• Challenges in Migrating from Dynamics NAV to Dynamics 365 Business Central — The most common obstacles in NAV-to-BC projects and how to overcome them
• Gestisoft Migration Services — How Gestisoft handles data transfer, system configuration, and go-live support for a migration to Dynamics 365
• Microsoft Dynamics 365 Business Central — Business Central's capabilities for Canadian SMBs in finance, manufacturing, and distribution
• What is ERP Consulting? Process, Benefits, Cost — How a certified ERP partner structures a migration engagement from first analysis to go-live
• How to Choose an ERP Software Using 10 Criteria — If you're still evaluating whether Business Central is the right ERP for your business, start here