There is no single “Dynamics 365 upgrade” procedure. The correct sequence depends on the Dynamics 365 application, your exact source release, whether it is online or on-premises, and whether you are applying an update, moving to a newer version, or migrating from an older Dynamics product. Record those four facts before scheduling technical work.
Use the matching Microsoft Learn route for your product as the technical authority. Business Central procedures differ by deployment model; Finance and Operations uses different processes for pre-version-8.0 upgrades and version-8.0-or-later updates; and NAV, AX, CRM, GP, and SL each have separate migration prerequisites. The workflow below helps you plan, test, and execute the project without treating unlike products as interchangeable.
As an Amazon Associate I earn from qualifying purchases.
1. Define exactly what “upgrade” means in your environment
Create a one-page project record before changing anything. It should name the application, source release, hosting model, target release or service, companies in scope, and the business reason for the change. Also classify the work as one of these:
- In-place update: applying a supported service or binary update to an existing deployment.
- Version upgrade: moving between official product releases, often with code and data conversion.
- Migration: moving data and functionality to a different deployment model or product service, such as NAV to Business Central online.
These labels affect downtime, data handling, custom-code work, and the environments you need. Microsoft’s Finance and Operations terminology is particularly important: a source environment before version 8.0 follows an “upgrade” process involving sandbox setup, code upgrade, and data upgrade. For a source on version 8.0 or later, Microsoft calls the work an “update”: you apply a binary package, with lower downtime requirements and no data upgrade. Read the current version guidance before committing because lifecycle routes change. See Microsoft’s Finance and Operations process guide.
#1 Best Overall
| Record | Why it changes the plan |
|---|---|
| Dynamics application | Business Central, Finance and Operations, or another legacy product has a different supported route and tooling. |
| Source version | Some releases require an intermediate version or a data/code conversion stage. |
| Hosting model | Online and on-premises deployments have different administration, access, and cutover steps. |
| Target | A newer release, an online service, or a reimplementation determines what data and customizations can move. |
| Business objective | Regulatory support, security, integration changes, performance, or new functionality determines scope and acceptance tests. |
2. Confirm a supported route before touching production
Open the current Microsoft Learn overview for your product and write down every prerequisite, intermediate release, and tool it names. Do not assume that the newest target can be reached directly from your source. Business Central explicitly distinguishes online and on-premises paths; older NAV sources may need several on-premises upgrade stages before they can move online.
Microsoft states in its Business Central overview: “The upgrade process depends on different factors, including on your decision to deploy Business Central on-premises or move your solution online.” Read the full route at Upgrading to Dynamics 365 Business Central.
Questions to answer from the documentation
- Is the source release still within a supported migration window?
- Is an intermediate on-premises version mandatory?
- Which localization, country, or regulatory packages are available at the target?
- Which database, operating-system, runtime, or Integration Runtime prerequisites apply?
- Which customizations must be converted, removed, or rebuilt?
- What replication, sandbox, or environment limitations affect rehearsal?
For migrations from AX, CRM, GP, NAV, or SL, use the product-specific route in Microsoft’s Dynamics on-premises migration overview. That page treats the products as separate journeys rather than one generic procedure.
3. Business Central: distinguish an installation upgrade from NAV-to-online migration
Business Central has multiple supported scenarios. An existing Business Central deployment may follow an on-premises or online upgrade path, while a NAV-to-Business-Central-online project follows a documented migration roadmap. Do not combine those instructions.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
The six phases for NAV to Business Central online
- Prepare the migration. Confirm the source version, target eligibility, localization, data scope, customizations, and technical prerequisites. Clean data and decide how companies will be batched.
- Upgrade NAV to a supported Business Central on-premises version. Older NAV releases may require more than one intermediate stage. Follow the version sequence Microsoft lists; do not invent a shortcut.
- Configure cloud migration. Set up the required connection, including the Integration Runtime where the Microsoft procedure calls for it, and establish the replication schedule.
- Replicate and validate data. Run replication in a non-production setting first. Check row counts, master data, opening balances, dimensions, attachments where applicable, and error logs against the source.
- Perform the data upgrade and complete migration. Execute the target data-upgrade steps during the approved cutover window, then validate business processes and integrations.
- Follow up after migration. Enable users, reconnect or validate integrations, monitor performance, and resolve post-cutover issues.
The authoritative procedure, including current prerequisites and limitations, is Migrate Dynamics NAV to Business Central online.
Full migration versus reimplementation
Microsoft describes two materially different NAV routes. In a full migration, custom code must be converted to AL extensions. Data in tables affected by code customizations cannot simply be carried forward unless those customizations are handled through extensions. This route is appropriate when preserving a broad operating history and established behavior is more important than redesigning the solution.
The documented Business Central 14 reimplementation route is narrower. It migrates essential business data such as master data, opening balances, and setup, rather than carrying forward the same customizations and all historical transactions. Treat that as a product-specific option, not a universal feature of every Dynamics migration. Decide explicitly which history, setup, documents, and audit records must remain accessible, and how legacy records will be retained if they are not loaded into the new tenant.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →| Decision factor | Full migration | Documented reimplementation route |
|---|---|---|
| Customization continuity | Convert relevant code customizations to AL extensions. | Replace or redesign custom behavior; the same legacy customizations are not carried forward. |
| Data and history | Designed to retain a broader operational data set, subject to table and extension constraints. | Essential master data, opening balances, and setup; not all historical transactions. |
| Preparation effort | Extension conversion, data preparation, company batching, and repeated migration tests. | Data mapping and validation plus a deliberate archive strategy for excluded history. |
| Best fit | Organizations that need continuity of processes and records. | Organizations willing to redesign and start with a controlled data set. |
These comparisons are practical implications of Microsoft’s NAV guidance, not a universal scoring system for every Dynamics product.
4. Finance and Operations: separate service updates from custom-code changes
For Finance and Operations implementations, plan Microsoft service updates and your custom-code lifecycle as related but separate workstreams. Microsoft recommends incremental lifecycle phases with development, functional test, user-acceptance testing (UAT), and production environments, plus version-controlled branches.
A service update may be runtime backward-compatible while not being design-time or compile-time backward-compatible. Compile and test custom code in the relevant development path before promoting it. Microsoft’s guidance puts the reason plainly: “By taking Microsoft updates without bundling them with custom code updates, you help simplify the update process.” Follow the current practices in Manage finance and operations updates and your custom code lifecycle.
A practical Finance and Operations branch flow
- Import the Microsoft service update into the designated development environment.
- Compile extensions and custom code, then resolve design-time and compile-time issues.
- Run functional and regression tests against critical processes, security roles, reports, and integrations.
- Promote the tested combination to a functional-test environment.
- Run UAT with representative users and realistic data, recording formal sign-off.
- Schedule production deployment only after rollback, support, and communications plans are approved.
For source environments before version 8.0, include the documented code-upgrade and data-upgrade activities. For version 8.0 and later, verify that the selected binary update path really applies to your release and topology; the absence of a data upgrade does not remove the need for regression and integration testing.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems5. Inventory customizations, data, integrations, and security
Do not estimate the project from the application version alone. Build an inventory that can be checked off and assigned to an owner.
Rank #4
Custom code and extensions
- List every customization, extension, modified object, report, workflow, batch job, and localization change.
- Record its business owner, source repository or package, dependencies, and target replacement.
- Identify code that touches tables or processes affected by the target migration.
- For NAV-to-online full migration, plan AL extension conversion before expecting the associated data to move.
Data and history
- Classify master data, setup, opening balances, transactional history, documents, attachments, audit records, and archived data.
- Remove duplicates, invalid references, obsolete dimensions, and unneeded records where policy permits.
- Define reconciliation totals for each company: general-ledger balances, subledgers, inventory, customers, vendors, and open transactions.
- Document retention, export, and read-only access for history excluded from a reimplementation.
Integrations and dependencies
- Inventory APIs, file exchanges, payment services, tax systems, warehouse or payroll connections, reporting feeds, identity providers, and scheduled jobs.
- Record endpoint owners, credentials or certificates, firewall rules, data contracts, retry behavior, and test contacts.
- Plan when each integration is paused, repointed, reauthenticated, and verified during cutover.
Security and operations
- Map current users and duties to target security roles; remove obsolete access and document segregation-of-duties decisions.
- Confirm administrators, service accounts, monitoring, backup or export responsibilities, and incident escalation.
- Identify country or industry localization requirements and verify their availability at the target.
6. Choose the migration scope and operating model
Route selection is not only a technical decision. Compare the destination and the continuing responsibility for updates, support, integrations, and monitoring.
| Question | Online destination | On-premises destination |
|---|---|---|
| Administration | More platform operations are managed by the service; tenant configuration and application responsibilities remain yours. | Your team or provider retains infrastructure, database, patching, capacity, and availability responsibilities. |
| Migration prerequisites | May include intermediate versions, cloud-migration configuration, Integration Runtime, replication, localization checks, and dry runs. | Depends on the product and supported release; infrastructure and compatibility prerequisites remain central. |
| After go-live | Plan user enablement, integration reconnection, release testing, and performance monitoring. | Plan the same application controls plus infrastructure monitoring, backups, and maintenance. |
| Customization strategy | Use the target extension and platform model; unsupported legacy modifications must be replaced or converted. | More deployment control may be available, but only supported customizations and versions should be retained. |
There is no defensible universal price, duration, downtime, or success rate for a Dynamics upgrade. Effort is driven by source release, number of companies, data quality, custom-code conversion, integrations, localization, and rehearsal results. Build the estimate from your inventory and test evidence rather than an industry average.
7. Prepare environments and data before the first rehearsal
- Provision the path. Establish development, functional-test, UAT, and production environments appropriate to the product. Keep configuration and code in version control.
- Prepare representative data. Use a sanitized but realistic copy or a documented subset that exercises high-volume and exception cases. For NAV migration, complete the required company batching, Integration Runtime connection, and replication schedule configuration.
- Document configuration. Capture legal entities or companies, number sequences, dimensions, posting groups, tax settings, workflows, reports, roles, and integration endpoints.
- Set quality gates. Define acceptable reconciliation tolerances, error thresholds, performance targets, and who can approve each stage.
- Protect the source. Verify backups or exports, restore procedures, access controls, and a freeze policy for changes during the migration window.
8. Test the complete route, not just the technical import
Microsoft’s go-live guidance calls for repeated migration tests and validation of data quality, timing, and risks. A successful import is not proof that the business can operate.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Test layers
- Data validation: reconcile record counts, balances, open items, dimensions, dates, statuses, and required fields.
- Functional testing: execute procure-to-pay, order-to-cash, inventory, finance close, budgeting, approvals, and other processes actually used by your organization.
- Integration testing: send and receive realistic messages, verify transformations, test failures and retries, and confirm monitoring alerts.
- Security testing: sign in as representative roles and prove that permitted and prohibited actions behave correctly.
- Performance testing: exercise peak volumes, batch jobs, reports, and concurrent users where capacity or timing is a concern.
- Regression testing: rerun critical scenarios after each code, configuration, or service-update change.
- UAT: have business owners approve results using agreed acceptance criteria, not informal demonstrations.
Record the duration of extraction, replication, data upgrade, validation, and integration reconnection during each rehearsal. Use the slowest credible run, plus an agreed contingency, to set the production window. Every failed rehearsal should produce a corrective action and a new run; do not waive a defect merely because the final date is approaching.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
9. Build and rehearse the cutover plan
A cutover plan is an executable schedule, not a paragraph in a project status report. Assign one owner and one verifier to each task.
- Announce the transaction freeze and confirm the final source backup or export.
- Disable or queue inbound integrations and scheduled jobs according to the dependency map.
- Run the final extraction, replication, or package deployment using the documented product procedure.
- Execute the data upgrade or migration steps and capture logs and errors.
- Reconcile control totals and investigate every material difference.
- Apply configuration, extensions, reports, workflows, and security roles that are part of the approved release.
- Reconnect integrations, rotate or validate credentials and certificates, and run end-to-end messages.
- Obtain technical and business sign-off against the acceptance checklist.
- Enable users in waves if that reduces risk; communicate the support channel and known limitations.
- Keep the rollback or contingency decision point explicit, with criteria and an owner.
Run this sequence at least once as a mock cutover with production-like data and timing. Microsoft’s go-live checklist emphasizes multiple dry runs, migration validation, and readiness checks.
10. Verify production readiness and go live
Before approving production, confirm all of the following:
- Functional, integration, performance, regression, and UAT results are signed off by named owners.
- Migration reconciliations meet the agreed thresholds and exceptions have documented disposition.
- Users are trained on changed processes and assigned appropriate security roles.
- External dependencies, integrations, certificates, batch schedules, reports, and support contacts are ready.
- Monitoring, alerting, backups or exports, and incident escalation are active.
- The cutover timetable, communications, validation scripts, and contingency plan are accessible to the team.
- Business, technical, and support leaders agree on the go/no-go decision.
Microsoft’s broader readiness guidance is available at Prepare your production environment to go live. Use it alongside the product-specific migration instructions, not as a replacement for them.
11. Monitor the first operating period
Keep enhanced support in place after users are enabled. Watch failed integrations, posting errors, batch queues, response times, security complaints, reconciliation differences, and user workarounds. Compare actual behavior with the test evidence and cutover assumptions.
For NAV-to-online migrations, Microsoft specifically calls for enabling users, reconnecting integrations, and monitoring performance as follow-up activities. For Finance and Operations, continue the branch and environment discipline for the next service update rather than treating go-live as the end of lifecycle work.
Common failure modes and corrective actions
| Failure mode | Why it happens | Corrective action |
|---|---|---|
| Following the wrong product guide | The team searches for “Dynamics upgrade” without identifying the application and source release. | Stop and classify the system; restart with the matching Microsoft Learn route. |
| Assuming a direct jump | An older NAV or other source is treated as compatible with the newest target. | List and execute every required intermediate version from the supported path. |
| Legacy code blocks data migration | Custom table or code changes are not represented as target extensions. | Convert, redesign, or remove the customization and repeat migration tests. |
| History disappears unexpectedly | Reimplementation scope is confused with full migration. | Approve the retained-data list and archive or provide read-only access to excluded history. |
| Service update breaks compilation | Runtime compatibility is mistaken for design-time or compile-time compatibility. | Compile and test custom code in development before promotion. |
| Cutover overruns | Timing was estimated without a production-like rehearsal. | Measure each task in mock cutovers, remove bottlenecks, and set a documented contingency. |
| Users cannot work on day one | Training, roles, integrations, or support ownership were left until the end. | Make each a signed readiness gate and test with representative users. |
12. A concise decision checklist
- Have we named the exact Dynamics application, source version, hosting model, and target?
- Is this an update, a version upgrade, or a migration?
- Does Microsoft document a supported direct route, or are intermediate releases required?
- Which customizations, extensions, reports, integrations, localizations, and security roles must change?
- What data and history must be retained, and is full migration or reimplementation appropriate?
- Are development, test, UAT, and production environments available and controlled?
- Have we completed data preparation, company batching, replication configuration, or other product prerequisites?
- Have realistic migration rehearsals produced acceptable reconciliation and timing?
- Are cutover owners, verification steps, communications, rollback criteria, and support assigned?
- Are users trained, roles validated, integrations connected, and monitoring active?
If any answer is “no,” the project is not ready for production. Resolve the gap or formally accept the risk with the business owner; do not hide it inside the cutover window.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
