Migrate your SAP S/4HANA Cloud data

Business Partners are the master-data foundation of S/4HANA, covering both customer and supplier roles under a unified concept. We map the BP number, addresses, contact details, and payment terms directly. The role assignment (Customer vs. Supplier) is preserved as a flag during migration.

Materials represent items in the MM module with views for Purchasing, Sales, Storage, and Accounting. We migrate material numbers, descriptions, unit-of-measure conversions, and plant-specific data. Cross-plant material types require separate plant-level records.

The COA in S/4HANA uses a three-line item account structure (GL Account, Company Code, and Operating Concern). We map account numbers, descriptions, and the controlling area assignments. Country-specific chart variations are handled per company code.

Journal entries are document-based with header/line-item hierarchies, tax codes, and payment terms. Historical entries require careful volume planning because S/4HANA in-memory processing surfaces data-quality issues immediately. We scope document date ranges and validate posting keys during migration.

Open payables and receivables are represented as open items linked to Business Partners. We migrate the document number, amount, due date, and clearing status. Partially cleared items require line-item-level detail to reconstruct the aging accurately.

Sales documents follow the standard SAP document-flow structure from Quote to Order to Delivery to Billing. We map header conditions, line-item pricing, and the schedule lines for delivery dates. Incomplete document flows require careful sequencing during migration.

Purchase orders store header and item data including purchasing organization, plant assignment, and confirmation control. We migrate PO item data, delivery addresses, and purchasing info records. Schedules are preserved as sub-items under each PO line.

S/4HANA Cloud Public Edition supports the Enable Extended Workspace Configuration (EEWC) framework for custom fields. These fields appear in the UI via the Adapt UI feature but require explicit activation per business context. We map custom field data alongside standard fields and flag any that reference unenumerated contexts.

Projects in the Project System module include WBS elements, networks, and activity elements. We map project hierarchies and the assignments of billing plans and cost planning data. Deeply nested WBS structures require recursive element extraction.

S/4HANA user accounts map to business roles and restrict data access at the field level via restriction fields. We migrate user assignments and their role mappings but destination role structures differ significantly, requiring explicit re-role mapping.