How to migrate from Dynamics NAV to Sage X3
To migrate a client from Dynamics NAV to Sage X3 with superglue's AI agent, connect the client's NAV database, and give superglue access to the client's Sage X3 account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs trial loads that reconcile to the cent before cutover. You review, decide and sign off with the client.
Microsoft's extended support for NAV 2018, the last NAV version, ends in January 2028, so most NAV clients plan their move now.
What are the steps to migrate from Dynamics NAV to Sage X3?
Migrating from Dynamics NAV to Sage X3 takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run trial loads and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect Dynamics NAV and Sage X3
Connect the NAV database on SQL Server read-only. superglue writes nothing. The client then gives superglue access to Sage X3.
- 02
Assess the Dynamics NAV data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the Dynamics NAV specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial loads
superglue loads a Sage X3 test folder and compares it with Dynamics NAV: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. superglue explains every difference, and you repeat the trial load until a full run reconciles with no new differences. The last run is a timed rehearsal of the cutover.
- 06
Cut over
At cutover, the client stops entry in Dynamics NAV, and superglue loads the open items with the same steps as the trial loads. After the client closes the last period in Dynamics NAV, superglue loads the final balances, and you sign the reconciliation with the client.
How do you get the data out of Dynamics NAV?
- The client's IT creates a read-only SQL Server login for the NAV database, and the superglue gateway reaches the server on the client's network.
- NAV versions before NAV 2013 may run on the native database, which needs a move to SQL Server or an export first.
- Each company has its own tables, so list every company in scope.
- Ask whether the client ran date compression. Compressed years keep one combined entry per period for each account, customer or vendor, so their detail cannot move.
The client installs the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Sage X3?
The client adds a Sage X3 user for superglue and names the folder superglue loads into. superglue configures Sage X3 and loads the data through that access, in a Sage X3 test folder first, in this order:
- 01
The charts of accounts and the analytical dimension types.
- 02
The ledgers and the account core model.
- 03
Companies and sites, with the legislation and the currencies of each company.
- 04
The fiscal years and periods of each company, and the dimension values.
- 05
Accounting codes, payment terms and tax codes.
- 06
Customers, suppliers and products, then the opening balances and the open items through import templates.
What moves from Dynamics NAV to Sage X3?
| In Dynamics NAV | In Sage X3 |
|---|---|
| Chart of accounts | General accounts |
| Dimensions and dimension values | Analytical dimensions |
| Customers | Customers |
| Jobs | Projects |
| Vendors | Suppliers |
| Items | Products |
| Bank accounts | Bank accounts |
Open items
Open customer and vendor ledger entries, open sales and purchase documents, and item ledger entries with their remaining quantity and cost.
Open items load as customer and supplier open items with their original numbers, dates and due dates, so the aging in Sage X3 matches on day one.
History
NAV keeps every ledger entry since the first posting unless someone ran date compression, which combines the entries into one per period for each account, customer or vendor. superglue reads the entries per company and per fiscal year.
History loads as journal entries per period, account and dimension.
Which decisions do you make when you migrate from Dynamics NAV to Sage X3?
- 01
Which NAV dimensions move?
NAV has two global dimensions, eight shortcut dimensions and any number of other dimensions on each entry. Sage X3 limits how many dimension types each ledger carries.
superglue lists the dimensions used on posted entries, and proposes dimension types only for those the client reports on.
- 02
What replaces NAV posting groups?
NAV picks accounts through customer, vendor and inventory posting groups and the general posting setup. Sage X3 picks them through the accounting codes on customers, suppliers and products, and the automatic journals.
superglue proposes an accounting code for each posting group in use, and checks the postings of the automatic journals against the NAV general posting setup.
- 03
How many companies and sites does the client need?
In Sage X3, a company keeps the legal books, and sites hold the financial, sales, purchasing, inventory and production activity.
superglue recommends one company for each legal company in Dynamics NAV, and a site for each location that keeps inventory or its own books.
- 04
Which analytical dimensions does the client need?
Sage X3 records analytical dimensions on journal lines, each account can require or default them, and the client chooses which dimension types to use.
superglue proposes dimension types from the segments and fields the client actually reports on.
- 05
Which cutover date does the client use?
A cutover on the first day of a period lets the open items and balances load as of one date. A fiscal year start keeps the year's reports and year-end filings in one system, and a date in the middle of the year means combining two systems for the audit and the tax returns. Avoid a date when the team must close the books or report results.
superglue recommends the first day of a month, and the first day of the fiscal year when the client can wait for it. The final balances load after the last period in Dynamics NAV is closed.
- 06
How much history moves?
Most clients need the open items plus one to three years of monthly balances in Sage X3, at least the current and the prior fiscal year for comparison, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from Dynamics NAV to Sage X3?
Customizations live in the database code
NAV customizations are written in C/AL inside the database, and they do not carry over to a new system. superglue lists the custom fields and tables that hold data, so you decide what moves.
Posting groups decide the accounts of documents
General, customer, vendor and inventory posting groups decide which accounts each sales, purchase and inventory entry hits. superglue maps each combination in use to the account defaults in the new system.
Retire old dimension values before the mapping
Years of projects and campaigns leave thousands of NAV dimension values, many of them blocked. Agree with the client which ones still matter, because every value that moves needs a mapping. superglue counts how often each value was used.
Multi-company clients need an intercompany plan
Clients with several companies keep one set of tables for each, with intercompany balances between them. Agree early which companies merge, which become entities, and how the intercompany balances settle. superglue reads every company and matches the intercompany balances.
Every object loads through its own import template
Sage X3 imports each object through an import template, with the same checks as manual entry, and the import log lists every record that fails. superglue builds the import files and explains every rejected record.
Customers and suppliers are business partners
Sage X3 keeps each trading partner once as a business partner, which can be a customer, a supplier or both. Agree with the client how duplicates across the old customer and vendor lists merge.
Activity codes switch features on
Sage X3 turns features and field sizes on with activity codes. Some are set when the folder is created, and every change needs a folder revalidation. Agree the activity codes in the design phase.
Open items must not count twice
Open invoices and bills post to the receivables and payables accounts when they load, and the opening trial balance holds the same amounts. Load the open items and the opening balances against one conversion account, and check that it ends at zero.
Plan fixed assets as their own stream
The trial balance brings the cost and the accumulated depreciation, but the asset register needs each asset with its in-service date, useful life and depreciation to date, and tax books need their own values. Agree early where the register lives after go-live, and reconcile it to the asset accounts.
superglue also runs the rest of the Sage X3 project. See the Sage X3 implementation
Frequently asked questions
Which data moves from Dynamics NAV to Sage X3?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Sage X3.
Does superglue write to Sage X3 without my approval?
No. superglue only reads Dynamics NAV. Before any write to Sage X3, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against Dynamics NAV: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Northwind Outdoor Supply, a sample client.
Start your Dynamics NAV to Sage X3 migration
Sign up and connect the client's systems, or let superglue set up Northwind Outdoor Supply, a sample client, to see a full migration run first.