// Source System
SAP to Dynamics 365 Data Migration
We've moved General Ledger, AR/AP and Fixed Assets out of SAP ECC into D365 F&O — cleanly, completely, on time.
SAP ECC — Entity Mapping
// The Challenge
Why SAP migrations are hard.
SAP ECC is one of the most common source systems we migrate from, and one of the most demanding. Customer and vendor master data is split across general (KNA1, LFA1) and company-code (KNB1, LFB1) tables, so a single D365 customer or vendor record often has to be assembled from two SAP tables rather than one.
The general ledger runs through SKA1/SKB1 for the account master and BSEG for line items. Open items in BSEG carry clearing document links that reference other line items — migrate them without preserving that chain and your AR/AP ageing will be wrong from day one.
Fixed assets in ANLA/ANLC are held by depreciation area, and SAP often runs several areas in parallel (book, tax, group). Deciding which area maps to D365's net book value is a design decision, not a data-mapping afterthought. Material master data in MARA/MARC frequently spans multiple plants and valuation classes, which needs to be rationalised against D365's single item structure before it moves.
// Mapping
SAP entities, mapped to D365.
| Source entity | D365 entity |
|---|---|
| KNA1 / KNB1 — Customer master | CustTable / CustCreditManagement |
| LFA1 / LFB1 — Vendor master | VendTable |
| SKA1 / SKB1 — GL account master | MainAccount |
| BSEG — GL line items | GeneralJournalAccountEntry |
| ANLA / ANLC — Asset master & values | AssetTable / AssetBook |
| MARA / MARC — Material master | InventTable / InventDim |
// Pitfalls
Where SAP migrations go wrong.
- Multiple chart of accounts per company code — reconciling to a single D365 chart requires a mapping decision early, not at cutover.
- SAP's KNA1/KNB1 split between general and company-code customer data doesn't map cleanly to a single D365 customer record — plan the merge before you build.
- Open AR/AP items in BSEG carry clearing document links that break if migrated without preserving the original document chain.
- Asset values in ANLC are stored by depreciation area — decide which area maps to D365's book value before transformation, not during UAT.
- Multiple SAP company codes sharing one chart of accounts often need to be split or consolidated to fit D365's legal entity model.
// Domains
Domains we most commonly migrate from SAP.
// Methodology
The same six phases, every time.
01
DISCOVER
Profiling, volumes, quality scoring across every source system in scope.
02
DESIGN
Source-to-target mapping and the cleansing plan, agreed before build starts.
03
BUILD
DMF templates, KingswaySoft packages, SQL staging tables.
04
TEST
Two mock migrations, full reconciliation, and UAT sign-off.
05
CUTOVER
Final load, balance reconciliation, go-live clearance.
06
STABILISE
Corrections, closure report, retainer option for what follows.
// FAQ
Questions about migrating from SAP.
Yes — the underlying table structures are largely consistent between ECC and S/4HANA, though S/4HANA's universal journal (ACDOCA) changes how GL line items are extracted.
Planning a SAP to D365 migration?
Start with a Health Check to see exactly what needs cleansing before it moves.