Migrate from SAP S/4HANA Cloud to Acumatica

SAP Business Partner is a single entity covering both customer and vendor roles. We split on BP role (KUNNR for customers, LIFNR for vendors) into separate Acumatica Customer and Vendor records. Where a BP carries both roles in SAP, both Acumatica entities are created and linked by the original BP number stored in Source_System_ID__c on each record.

SAP Material Master carries material type (ROH, HALB, FERT, HAWA), procurement type (in-house/external/both), and valuation class. We map material type 'ROH'/'HALB'/'FERT' to Acumatica Stock Item with ValuationGroupID derived from SAP valuation class; 'DIEN'/'KMPF' map to Non-Stock Item. Basic Unit of Measure becomes Item UOM; alternate UoMs are stored in Acumatica's UoM conversion table if fewer than three exist, otherwise flagged for post-migration cleanup.

SAP Flexible General Ledger charts of accounts with up to 10 segments are flattened into a single Acumatica Account.cd3 account code. We concatenate the primary segment (typically company-code-level account number) with secondary segments using a delimiter of your choice. All additional segment values are stored in Custom_SAP_GL_Segment_Ref__c on the Acumatica Account for post-migration Cost Code assignment. Account type (balance sheet vs. P&L) is mapped from SAP's chart-type field (SATYP).

SAP Cost Center (KOSTL) maps directly to Acumatica Cost Code. The SAP Cost Center hierarchy (controlling area level) is preserved as a parent-child relationship in Acumatica Cost Codes. Functional area assignments from SAP are stored in CostCodeCategory__c on the Acumatica Cost Code. Users recreate cost center-based reporting in Acumatica's Report Designer using Cost Code as the primary dimension.

SAP separates Purchasing Requisitions (ME51N) from Purchase Orders (ME21N) as distinct documents. Acumatica has one Purchase Orders screen that covers both planned and released orders. We map SAP PO header and line data directly; SAP requisitions without a released PO are loaded as Acumatica purchase orders in Draft status, with the original requisition number preserved in Custom_SAP_PO_Number__c. Release strategy codes are not replicated — your Acumatica admin implements approval workflows post-migration.

SAP Sales Document (VA01/VA02) maps to Acumatica Sales Order with full header and line-level detail. SAP sales area (sales org / distribution channel / division) is stored as Custom_SAP_SalesArea__c on the Acumatica header. Pricing conditions from SAP (KONV) are mapped to Acumatica manual line adjustments where the number of conditions is fewer than five; complex multi-condition structures are flagged for Acumatica price manager configuration post-migration.

SAP FI Invoice (FB60 for vendors, FB01 for GL direct) maps to Acumatica Bills (vendors) and Invoices (customers). Invoice line items are mapped to Acumatica bill/invoice details with account or project reference. Payment terms from SAP (ZTERM) are stored in Custom_SAP_Payment_Terms__c on the Acumatica bill; your admin configures matching Payment Terms in Acumatica's Terms editor post-migration.

SAP Fixed Asset Master (AS01) maps to Acumatica Fixed Asset. Depreciation area assignments from SAP are not replicated — Acumatica calculates depreciation on its own depreciation schedule. Useful life, acquisition date, acquisition cost, and accumulated depreciation are preserved from SAP fields ANLA-aktiv, AKTFN, and AFAVC. Asset class (ANLA-ANLKL) is stored as Custom_SAP_Asset_Class__c on the Acumatica asset.

SAP Project System (CJ01) projects map to Acumatica Projects where the SAP PS module is active. WBS elements map to Acumatica Project Tasks with the WBS hierarchy preserved as task parent-child relationships. Network activities map to Project Tasks of type Labor. Revenue and cost planning lines are stored in Custom_SAP_Planning_Data__c for reference; your Acumatica project accountant rebuilds budget tracking within Acumatica's Project Budget module.

SAP Custom Fields added via Custom Fields and Logic (SAP S/4HANA Cloud) or customer-specific appends are exported with the standard entity. Each custom field requires an equivalent Acumatica custom field created in the Customization Project editor before migration runs. Custom field labels and help text from SAP are exported as reference documentation for your Acumatica admin during field creation. Fields on SAP-delivered tables that cannot be extended require a custom Acumatica screen or note field.

SAP Business Partner can hold multiple addresses per role (headquarters, purchasing, remittance). Acumatica stores one primary address per Customer or Vendor. We map the SAP address flagged as the 'Primary' address for each role to the Acumatica primary address. Any additional SAP addresses are stored as a JSON-formatted reference in Custom_SAP_Additional_Addresses__c on the Acumatica entity, available for manual distribution to contacts or shipping addresses post-migration.

SAP Valuation Class controls which G/L accounts are posted for inventory transactions. Acumatica uses ValuationGroupID on Stock Item to determine valuation method (Standard, Average, FIFO). We map SAP valuation class to Acumatica ValuationGroupID and store the original SAP valuation class in Custom_SAP_Valuation_Class__c on the Stock Item. Where SAP maintains multiple parallel valuations per material, the primary (company-code-level) valuation is used; secondary valuations are preserved in the custom field reference for cost-audit purposes.