SAP ECC support ends Dec 2027. Migrating to D365 F&O is viable but requires translating company codes to legal entities, material masters to released products, and GL line items to the voucher model.
There is no native migration path from SAP ECC to Dynamics 365 Finance and Operations; the two platforms use fundamentally different data models, meaning every major data entity—from company codes to material masters to GL line items—requires structural translation rather than a simple table-level transfer. SAP's monolithic record structures (e.g., material master views, controlling areas, BKPF/BSEG financial documents) must be decomposed and remapped to D365's party model, financial dimensions, released product architecture, and voucher/journal framework. Custom transformation logic, strict import sequencing through D365's Data Management Framework (DMF), and active ledger dimension format validation are required for every data domain, making this a re-implementation-grade effort rather than a lift-and-shift.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
If you're running EHP 0–5, mainstream maintenance already ended on December 31, 2025
You're in customer-specific maintenance now unless you've upgraded to EHP 6–8.
When SAP is still the right call
If you operate in 50+ countries with deeply customized manufacturing modules, complex variant configuration, or intricate intercompany transfer pricing, SAP's functional depth in those areas may still be unmatched. This isn't a "D365 always wins" argument — it's about knowing where the trade-offs fall for your specific operations.
Archive first, migrate second
Cleanse and archive historical data in SAP before extraction. This reduces extraction volume, speeds up mock cutovers, and forces the team to make data retention decisions early — not during UAT.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Scope the ledger, the subledgers and the audit obligations.
Objective Agreed scope across master data, open transactions and historical balances, with finance and audit signed up.
Keep these open
-
Inventory master data and transaction volumes in SAP ECC
Count GL accounts, customers, vendors, items, fixed assets, open AR and AP, and transaction lines by year. Transaction line volume, not header count, is what determines your load time.
Data Profiler Get real record counts instead of estimating from memory -
Decide the history strategy with finance and audit
Choose between opening balances only, open items plus balances, or full transactional history. This is the single biggest scope decision in an ERP migration: full history multiplies effort many times over, and most organisations land on balances plus open items plus a read-only archive.
Full transactional history is rarely worth the cost. Confirm what your auditor actually requires before assuming you need it.
Vendor Evaluator Score Dynamics 365 Sales against alternatives on weighted criteria -
Consult the external auditor early
The auditor has views on cut-over timing, audit-trail retention and how you evidence that balances carried across correctly. Finding this out after go-live can mean a qualified opinion, so get it in writing now.
-
Review the chart of accounts and decide whether to redesign
A migration is the natural moment to restructure the COA, and also the riskiest one. If you redesign, you need a mapping from old to new for every historical balance, plus a plan to restate comparatives.
Redesigning the chart of accounts mid-migration doubles the reconciliation burden. Treat it as a separate, sequenced project if you can.
-
Catalogue integrations and statutory reporting
List banking feeds, payment gateways, tax filing, payroll, CRM, e-commerce, warehouse and BI. Then list every statutory and tax filing obligation with its deadline — those deadlines constrain your window absolutely.
-
Pick a period-aligned go-live date
ERP cutovers align to a period boundary — ideally the start of a fiscal year, otherwise the start of a clean month. Mid-period cutover means split-period reporting for the rest of the year.
SAP ECC → Dynamics 365 Sales specifics
- Extended maintenance through December 31, 2030
- , at a two-percentage-point premium on your maintenance base — roughly a 9% cost increase.
- Customer-specific maintenance
- , which provides no new security patches, no legal change packages, and no support packages.
Don't move on until
- Chart of accounts and master-data counts confirmed
- History strategy agreed: balances, open items, or full transactional detail
- External auditor consulted on the migration approach
02 Data Audit Reconcile the source before you migrate it — you cannot fix a ledger later.
Objective A source ledger that balances, with master data cleansed and every open item agreed.
Keep these open
-
Produce and sign off a source trial balance
Run the trial balance in SAP ECC and have the controller sign it. This is your migration baseline: without a signed pre-migration position you have nothing to reconcile the target against, and any later discrepancy is unarguable.
Without a signed, dated source trial balance you cannot prove the migration preserved the ledger. Do this before anything else.
-
Reconcile subledgers to the general ledger
Confirm AR, AP, inventory and fixed-asset subledgers tie to their GL control accounts. Pre-existing breaks must be resolved in SAP ECC: migrating an out-of-balance ledger makes the break permanently unattributable.
Data Profiler Profile the SAP ECC export for nulls, outliers and type drift -
Clean and deduplicate master data
Deduplicate customers, vendors and items, and identify records that should not carry forward. Duplicate vendors are also a fraud-control weakness, so this has value beyond the migration.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Agree open AR and AP item by item
Every open invoice, credit note and payment on account needs an owner and an agreed amount, including partially-paid items and foreign-currency balances. Open items are what customers and vendors will dispute in week one.
-
Validate export structure, encoding and precision
Check numeric precision and rounding on the export, and confirm dates and currency codes are unambiguous. Precision loss on amounts is silent, cumulative and produces penny differences that take days to trace.
Amounts exported at reduced precision will not re-total. Verify decimal places before you accept the export.
CSV Validator Catch broken headers and ragged rows in the raw export -
Scan for regulated data and produce masked test data
ERP data holds bank details, tax IDs and payroll information. Scan it, restrict who can see it, and generate a masked copy for the sandbox and for any implementation partner.
PII & Compliance Scanner Find regulated fields before they land in a new system
Don't move on until
- Trial balance in SAP ECC balances and is signed by the controller
- AR and AP subledgers reconcile to the GL control accounts
- Master data deduplicated and inactive records identified
03 Field Mapping Map the COA, the dimensions and the subledger structures.
Objective A signed mapping covering the chart of accounts, dimensions, tax codes and currency handling.
Keep these open
-
Map the chart of accounts account by account
Every source account maps to exactly one target account, or to a documented split with agreed proportions. The controller reviews and signs this line by line — an unreviewed COA map is how a balance sheet stops balancing.
Schema Mapper Opens pre-loaded with the SAP ECC → Dynamics 365 Sales field pair -
Map dimensions, cost centres and analysis codes
ERPs differ structurally here: segments, dimensions, tracking categories and classes are not interchangeable. Confirm how Dynamics 365 Sales models analysis and whether your existing reporting hierarchy survives the translation.
-
Map tax codes, rates and jurisdictions
Map every tax code with its rate, jurisdiction and reporting treatment, then verify the mapping reproduces your last filed return. Tax errors are statutory exposure, not reporting inconvenience.
A tax-code mapping that has not been tested against a previously filed return is untested. Reproduce a real filing before sign-off.
-
Decide multi-currency and exchange-rate handling
Confirm functional and reporting currencies, and how historical rates are stored. Revaluing historical transactions at current rates rewrites reported results and will not tie to filed accounts.
Historical transactions must retain their original transaction-date rates, or your comparatives will not match filed statements.
-
Map master data and subledger structures
Map customer and vendor records with their payment terms, credit limits and tax registrations, and item records with units of measure and costing method. Costing-method differences change inventory valuation, which changes the balance sheet.
-
Set load order and freeze the spec
COA, then dimensions, then master data, then opening balances, then open items, then any historical detail. Version and sign off the spec with the controller before the pilot.
Don't move on until
- Account-by-account COA mapping reviewed by the controller
- Tax codes and jurisdictions mapped and verified against filings
- Multi-currency and rate handling agreed with finance
04 Test Migration Prove the ledger balances in the target before you trust it.
Objective A sandbox load whose trial balance matches the signed source position to the penny.
Keep these open
-
Configure the Dynamics 365 Sales sandbox with the agreed structures
Build the COA, dimensions, tax codes, currencies, fiscal calendar and posting rules before loading anything. Every one of these affects how a posted transaction lands, so an unconfigured sandbox produces meaningless results.
-
Load master data and validate it
Load customers, vendors and items first and verify counts, payment terms, tax registrations and costing methods. Transactions cannot post correctly against wrong master data, so this gate comes before any balance work.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Load opening balances and prove the trial balance ties
Load opening balances and run a trial balance in Dynamics 365 Sales, comparing to the signed source position. It must match exactly — a rounding difference here is a mapping defect, not a rounding difference.
Any variance at all between source and target trial balance must be explained line by line. "Close enough" is never acceptable in a ledger.
-
Load open items and reconcile the subledgers
Load open AR and AP with their ageing intact, then confirm subledger totals tie to GL control accounts and that ageing buckets match. Ageing that shifts means transaction dates mapped wrongly.
-
Run a full period-end close in the sandbox
Execute the whole close: revaluation, accruals, depreciation, tax calculation, and financial statement generation. Compare every statement to SAP ECC for the same period. The close is where structural mapping errors finally become visible.
-
Test transactions end to end and reproduce a tax filing
Post a sales order to cash and a purchase order to payment, then generate the tax return for a previously filed period and compare it to what you filed. If both reconcile, the configuration is sound.
Don't move on until
- Target trial balance matches the signed source trial balance exactly
- Subledgers reconcile to control accounts in the target
- A full period-end close has been run in the sandbox
05 Cutover Switch the ledger on a period boundary, with balances proven.
Objective Balances and open items live in Dynamics 365 Sales, transacting resumed, and a signed post-load trial balance.
Keep these open
-
Close the final period in SAP ECC and freeze posting
Complete the period-end close, then lock posting entirely. An ERP freeze is absolute: a single journal posted to the old system after the final export leaves the two ledgers permanently divergent.
One journal posted in the old ERP after the final export breaks the reconciliation permanently. Lock posting at the system level, not by asking people nicely.
-
Publish the cutover runbook with the abort point
A timed, owner-named sequence for load, balance verification, integration switch and go/no-go, with an explicit abort criterion. The trial-balance check is the gate — nothing proceeds until it ties.
-
Load balances and open items into production
Load the final opening balances and open AR/AP into Dynamics 365 Sales production, following the pilot-proven sequence. Do not improvise the order under time pressure.
-
Reconcile and sign the post-load trial balance
Run the trial balance in Dynamics 365 Sales and reconcile it to the signed source position, then have the controller sign the result. This signature is your evidence for the auditor and your go/no-go gate.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint banking, payment and tax integrations
Switch bank feeds, payment gateways, tax filing connections, payroll and BI, then process one real low-value payment and one bank reconciliation end to end. Banking errors move real money, so verify with live traffic.
Payment integrations left connected to the old ERP can duplicate real payments. Disable them before switching, not after.
-
Go/no-go, then open for transacting with daily reconciliation
Call the decision on the signed trial balance, open Dynamics 365 Sales for posting, and reconcile daily for the first two weeks with finance support on hand. Keep SAP ECC read-only for statutory retention — this is an audit requirement, not a preference.
Don't move on until
- Post-load trial balance signed by the controller
- Banking, tax and payment integrations verified live
- Users transacting and the first daily reconciliation clean
06 Validation Prove the statements, the tax position and the audit trail.
Objective Financial statements reproducing the source position, a clean tax filing, and auditor acceptance.
Keep these open
-
Reconcile the full ledger and all subledgers
Reconcile trial balance, AR, AP, inventory, fixed assets and bank against the signed source position. Produce a single reconciliation pack that goes to the auditor.
Migration Validation Tool Reconcile SAP ECC and Dynamics 365 Sales record-for-record -
Reproduce the financial statements
Generate balance sheet, P&L and cash flow in Dynamics 365 Sales and compare to the pre-migration statements. Every variance needs a documented explanation traced to a specific mapping decision.
-
Complete and review the first period-end close
Run the first real close in Dynamics 365 Sales with extra review at every step. Compare its duration and outcome to your historical close, and treat anything unexpected as a live finding.
Data Profiler Prove field completeness held up through the load -
Verify the tax position and file
Generate and review the first tax filing from Dynamics 365 Sales, reconciling it to the underlying transactions before submission. Have the tax lead review it independently.
The first statutory filing out of a new ERP should be reconciled manually to source transactions before submission.
-
Confirm controls, segregation of duties and audit trail
Verify user permissions, approval limits, segregation of duties and audit logging in Dynamics 365 Sales. Controls do not migrate, and a control gap found by an auditor is far more expensive than one you find yourself.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Obtain auditor acceptance and retain the archive
Walk the auditor through the reconciliation pack, get written acceptance, and retain SAP ECC read-only for the full statutory retention period. Diarise the retention expiry rather than the contract renewal.
Don't move on until
- Financial statements match the pre-migration position
- First period-end close completed and reviewed in Dynamics 365 Sales
- Auditor satisfied and archive retained for the statutory period
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Material Master Released Products
The monolithic SAP material master must be decomposed into shared products and per-entity released products with strict creation sequencing, often causing significant record multiplication.
| SAP ECC field | Dynamics 365 Sales field | Notes |
|---|---|---|
| MARA.MATNR (Material Number) | EcoResProduct.DisplayProductNumber | Direct map, validate alphanumeric limits |
| MARA.MTART (Material Type) | EcoResProduct.ProductType | Translate to D365 Enum (Item vs. Service) |
| MARC.WERKS (Plant) | InventLocation.InventLocationId | Map SAP Plant to D365 Site/Warehouse structure |
| MARA.MEINS (Base Unit) | UnitOfMeasure.Symbol | Map to D365 Unit of Measure conversions |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Legal Entities (Company Codes) | medium | The conceptual mapping is 1:1, but divergent surrounding structures like controlling areas and security boundaries require careful redesign rather than direct transfer. |
| Chart of Accounts | medium | D365 supports shared charts with legal entity overrides, which differs from SAP's structure and requires reconciliation of account hierarchies across all migrating company codes. |
| Financial Dimensions (Cost Centers/Profit Centers) | high | SAP's controlling area has no direct D365 equivalent, requiring a complete redesign of cost accounting structures into financial dimensions with validated dimension value combinations. |
| Products (Material Masters) | high | The monolithic SAP material master must be decomposed into shared products and per-entity released products with strict creation sequencing, often causing significant record multiplication. |
| Customers | high | SAP customer masters must be consolidated into D365's party model with duplicate detection, number sequence reconfiguration, and mandatory registration ID cleanup to avoid blocked invoice posting. |
| Vendors | high | Vendor masters face the same party model consolidation challenges as customers, with the additional risk of a single SAP entity existing as both customer and vendor requiring reconciliation into one party record. |
| GL Balances and Historical Transactions | high | Historical financial data must be imported as unposted journals and posted within D365, with every entry validated against the new dimension structure and Chart of Accounts—direct table insertion is not possible. |
| Sites and Warehouses (Plants/Storage Locations) | medium | SAP plant and storage location structures map to D365 sites and warehouses, but the more flexible D365 model requires explicit configuration rather than automatic translation. |
| Number Sequences (Document Numbers) | medium | SAP's configurable document number ranges do not carry over directly to D365's per-legal-entity number sequences, and gaps or overlaps between systems create reconciliation challenges. |
| Units of Measure | low | Unit of measure mappings are generally straightforward direct translations, though conversion factors must be validated against D365's unit of measure framework. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Controlling Area to Financial Dimensions
SAP's controlling area structure for cost accounting (cost centers, profit centers, internal orders) has no direct equivalent in D365 and must be completely redesigned as financial dimensions, requiring deep finance team involvement.
Material Master Record Explosion
SAP's monolithic material master must be split into D365's two-step product master and released product model, potentially multiplying record counts by the number of legal entities (e.g., 15,000 materials across 4 company codes becomes up to 60,000 released product records).
Customer/Vendor Party Consolidation
SAP's separate customer and vendor masters must be structurally consolidated into D365's global address book party model, requiring duplicate detection, name/address normalization, and tax registration cleanup before load.
GL Historical Balance Migration
SAP financial documents cannot be inserted directly into D365's posted tables; they must be loaded as unposted journals via DMF, validated against the new Chart of Accounts and financial dimensions, and then posted within D365.
Active Dimension Format Validation
D365 enforces a global active ledger dimension format on all imported transactions, and missing or incorrectly ordered segments cause import errors while extra segments may be silently dropped.
Import Sequencing and Dependencies
D365's data entities enforce strict relational integrity and creation order—for example, shared products must exist before released products can be imported—preventing bulk-loading of all data in a single pass.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
When does SAP ECC end of support happen?
SAP ECC 6.0 (EHP 6–8) mainstream maintenance ends December 31, 2027. Extended maintenance is available through 2030 at roughly a 9% cost premium. EHP 0–5 customers already lost mainstream support on December 31, 2025.
Can Dynamics 365 replace SAP ECC?
Yes, for most mid-market and upper-mid-market organizations. D365 Finance & Operations covers finance, supply chain, manufacturing, and HR. However, companies with highly specialized manufacturing, 50+ country operations, or deep SAP customizations should evaluate functional gaps carefully before committing.
How does SAP's company code map to Dynamics 365?
SAP's company code maps to D365's legal entity — both represent the smallest unit for statutory financial reporting. The key difference is SAP's controlling area (for cost accounting across company codes) has no direct equivalent; D365 uses financial dimensions instead, requiring a redesign of your cost accounting structure.
What SAP data should I migrate to Dynamics 365 vs. archive?
Migrate open AR/AP items, current-period plus prior-year GL balances, active master data (customers, vendors, products), current inventory, and active fixed assets. Archive everything older into Azure Data Lake or a read-only database for historical reporting.
How many mock cutovers are needed before go-live?
At least two. Microsoft's own implementation guidance requires at least one successful mock cutover and recommends practicing several times. In practice, two dress rehearsals is the safe minimum: one to expose problems, one to prove the fixes under realistic timing.