Migrate from SAP S/4HANA Cloud to Microsoft Dynamics 365 Business Central

SAP Business Partners with Customer role split into Dynamics 365 Account (the organization) and Contact (the primary individual). BP addresses, payment terms, and bank details migrate to Account; BP contact persons and communication data migrate to Contact linked via the AccountRelationship. We use the BP's address-usage roles (SO Business Address, PU Business Address) to determine which addresses attach to Account versus Contact. Duplicate detection uses BP number as external key with Dynamics Account Number populated accordingly.

SAP Business Partners with Vendor role split into Dynamics 365 Vendor (a special Account type in F&O) and Contact. The BP's purchasing address and payment terms migrate to the Vendor record; purchasing contacts migrate as Contact records linked to the Vendor. Vendor classification codes in SAP map to the Dynamics 365 Vendor group field.

SAP BPs with both Customer and Vendor roles produce a single Account in Dynamics 365 (the company) with two Contact records: one for the customer-facing relationship and one for the vendor-facing purchasing contact. Both Contact records share the same Account parent. We use BP category and address-role flags to disambiguate contact assignment during the transform phase.

SAP Materials map to Dynamics 365 released products with SAP material type (HALB, FERT, HAWA, ROH) mapped to Dynamics 365 product type. SAP unit-of-measure conversions migrate as inventory unit conversions in Dynamics 365. Plant-specific data maps to warehouses in the InventWarehouse table. Material master views (MM, SD, FI) map to Dynamics 365 product modules (Procurement, Sales, Inventory Management).

SAP GL accounts map to Dynamics 365 Main Accounts within a chart of accounts structure. SAP's company-code-level account plus controlling-area structure maps to the Dynamics 365 legal entity and financial dimension framework. Country-specific chart variants in SAP (for example, German commercial chart or US GAAP chart) require pre-migration Financial Dimension design sessions because Dynamics 365 uses Financial Dimensions as the primary cost-object reporting layer rather than SAP's operating-concern approach.

SAP financial documents (BKPF/BSEG) map to Dynamics 365 general journal lines. SAP document number becomes the Dynamics journal number or reference. SAP posting date, document date, and fiscal period map to the Dynamics 365 transaction date and fiscal period. SAP tax codes require mapping to Dynamics 365 Tax Engine tax groups and tax codes during the ETL phase. Historical entry volume drives bulk API strategy and timeline estimation.

Open SAP vendor invoices map to Dynamics 365 vendor invoice records with open amount, due date, and payment terms preserved. Partially cleared SAP invoices (partial payment received or partial goods receipt) require line-item split in Dynamics 365 or invoice-matching workflow adjustments. SAP's clearing document concept maps to Dynamics 365 settlement processes. Payment terms from SAP BP master data must be pre-loaded into Dynamics 365 before AP migration.

Open SAP customer invoices map to Dynamics 365 free-text invoices or sales invoices depending on the SAP invoice type. SAP's dunning procedure maps to Dynamics 365 collection letter sequences. Customer payment terms from BP master data must be loaded before AR migration. Overdue aging reports in SAP must reconcile against Dynamics 365 aging analysis before the AP/AR go-live gate.

SAP Sales Orders (VA01/VA02) map to Microsoft Dynamics 365 Sales Order with header conditions, line-item pricing, delivery addresses, and schedule lines preserved. SAP's schedule line delivery dates map to Dynamics 365 requested receipt dates. Sales area assignment (Sales Organization / Distribution Channel / Division) maps to Dynamics 365 Site and Warehouse assignments within the order. Incomplete or credit-blocked SAP orders are flagged for admin review before migration.

SAP Purchase Orders (ME21N/ME22N) map to Dynamics 365 Purchase Orders with header and item data, delivery addresses, and confirmation control preserved. Purchasing info records from SAP migrate as vendor product masters in Dynamics 365. Schedule lines with delivery dates map to expected receipt dates in the order. Contract-driven POs require the purchasing agreement (MPO or PA) to be migrated before PO records.

SAP Project System WBS elements, networks, and activity elements map to Dynamics 365 Project Work Breakdown Structure and task hierarchy. Project costing data and billing plan assignments migrate as project forecast lines and project contract lines. Deeply nested WBS structures (over 10 levels) require pre-migration flattening or Dynamics 365 task hierarchy redesign. Project accountant assignments in SAP map to Dynamics 365 project team roles.

SAP S/4HANA Cloud Public Edition custom fields created via Enable Extended Workspace Configuration (EEWC) require a replacement strategy in Dynamics 365. Fields added via the Adapt UI feature in SAP map to custom columns on the equivalent Dynamics 365 table. We audit all EEWC fields during discovery, capture their data types and table assignments, and pre-create the equivalent Dataverse columns or Dynamics 365 extension fields before data migration begins. SAP-side calculated fields without data storage do not migrate as data; they require Dynamics 365 calculated column or Power Automate flow replacement.

SAP Generic Object Services (GOS) attachments link to BP, material, and document records. We extract attachments from the SAP content server via the OData API and migrate them to SharePoint Online or Dataverse attachment tables linked to the equivalent Dynamics 365 record. File naming conventions preserve the SAP document service path. Migrations exceeding 10,000 attachments require Azure Blob Storage staging and batch processing.

SAP user accounts with business role assignments map to Dynamics 365 users with corresponding security roles. SAP field-level restriction fields (Restriction Fields on business roles) require a Dynamics 365 security role redesign because Dynamics 365 uses record-level security and field-level security separately rather than SAP's restriction-field model. SAP technical users used for integration mapping require manual provisioning as Dynamics 365 application users.