Migrate from SAP S/4HANA Cloud to Dolibarr ERP

SAP Business Partners (unified customer/vendor under a single BP number) map to Dolibarr Third Parties. In Dolibarr, a Third Party is created as either a customer, a supplier, or both. The SAP BP number becomes the Dolibarr ref_int field for cross-reference. SAP address roles (plant, sold-to, ship-to, bill-to) map to Dolibarr contact addresses with type labels. SAP payment terms from the BP master record become Dolibarr_cond_reglement entries. We split the unified BP into separate customer and supplier Dolibarr records if the source BP carries both roles and the destination requires separate tracking.

SAP contact persons attached to a Business Partner (BUT000/BUT050) map to Dolibarr contacts linked to the corresponding Third Party via the socpeople FK. SAP roles (contact person, employee responsible, partner function) become Dolibarr contact roles. We preserve the SAP contact's email, phone, and functional title in Dolibarr's contact fields. Any BP contact without an email address is flagged for manual enrichment during migration.

SAP Materials (MARAs) map to Dolibarr Products. SAP material type (HAWA for finished goods, HALB for semi-finished, ROH for raw material, VERP for packaging) maps to Dolibarr product type (0=product, 1=service). SAP units of measure from MARM map to Dolibarr unit_of_measure entries. The material number becomes Dolibarr's ref (with a length check; SAP 18-character keys are truncated to Dolibarr's 30-character limit without issue). Plant-specific stock data from MARD maps to Dolibarr stock_warehouse entries per warehouse.

SAP's three-line GL account structure (GL Account key plus Company Code plus Operating Concern) requires flattening for Dolibarr's simple chart of accounts. We extract the SAP COA using the Company Code as the primary segment, preserving account number and description. Dolibarr uses a flat account number scheme (the 'pcg_version' structure). We map the most-used SAP account types (assets, liabilities, expenses, revenues) to the nearest Dolibarr chart of accounts template (PCMN standard French plan or a custom export from SAP). Country-specific tax codes from SKA1/KNT1 map to Dolibarr tax categories.

SAP journal entries (BKPF/BSEG) map to Dolibarr accounting entries (accounting_bookkeeping table). Each SAP document header (BKPF) becomes a Dolibarr piece_comptable with document_date, doc_ref, and label preserved. Each SAP line item (BSEG) becomes a Dolibarr tab_accounting_accounting. We map SAP posting keys (BSCHL) to Dolibarr debit/credit amounts. Historical entries are loaded in date-order with validated date ranges. Entries with uncleared open items (BSEG-AUGBL not populated) are flagged as open and require subsequent clearing in Dolibarr.

SAP open receivables (BSEG with BUKRS=AR company code, KOART=K) map to Dolibarr customer invoices. The SAP customer BP becomes the Dolibarr Third Party; the invoice document number, amount, currency, and due date migrate. Open AR status is preserved as an unpaid Dolibarr invoice; partially cleared AR with partial payment history requires a payment record linked to the invoice. SAP's payment terms (ZTERM) map to Dolibarrcond_reglement.

SAP open payables (BSEG with BUKRS=AP company code, KOART=K) map to Dolibarr supplier invoices. The SAP vendor BP becomes the Dolibarr Third Party; invoice number, amount, currency, and due date migrate. Open AP status is preserved as an unpaid Dolibarr supplier invoice. SAP's payment block indicator (SPERZ) and release reason (FRGZU) are stored in Dolibarr custom fields because the standard Dolibarr invoice model does not include these SAP-specific flags.

SAP Sales Documents (VBAK/VBAP) map to Dolibarr commercial proposals (for quotations in status QUOT, ORD) or directly to Dolibarr orders for firm orders (status OB). SAP header conditions (KONV) map to Dolibarr total and subtotal lines. SAP line-item pricing, quantity, and delivery dates migrate as line items with discount information. SAP's schedule lines (VBEP) are consolidated into a single delivery date per line item because Dolibarr does not support multi-schedule-line sales orders natively.

SAP Purchase Orders (EKKO/EKPO) map to Dolibarr supplier orders (ask for quotation or purchase order depending on status). The SAP vendor BP becomes the Dolibarr Third Party; the PO number, currency, and incoterms (INCO1) migrate. Line items with material number, quantity, and net price migrate to Dolibarr purchase order lines. Delivery address from the SAP PO (ADRFP) maps to a Dolibarr contact address on the order. Confirmation control (BSTYP) and ordering party assignments are preserved in custom fields.

SAP PS module projects (PRPS) with WBS elements (PROJ/PRPS) map to Dolibarr Projects. The top-level WBS element becomes the Dolibarr Project; child WBS elements become sub-projects or tasks depending on nesting depth. SAP network activities (AFVC/AFVU) map to Dolibarr tasks with assigned resources and durations. SAP cost planning data (COSP/COVP) can be stored as Dolibarr expense entries linked to the project if the project's financial tracking is required. Projects without financial elements are migrated as operational Dolibarr projects only.

SAP S/4HANA Cloud custom fields created via the EEWC framework and exposed in the UI via Adapt UI map to Dolibarr extrafields. We audit the full list of active custom fields in SAP, map their data types to Dolibarr field types (varchar, int, datetime, select, chkbx, etc.), and pre-create the extrafields schema in Dolibarr before data migration. Fields that reference SAP-specific domain values (plant lists, company-code-specific picklists) may require a Dolibarr dictionary entry as the replacement lookup table. Custom fields on custom business objects follow the same pattern with the additional step of creating the corresponding Dolibarr module and table if the underlying module does not exist.

SAP users with assigned business roles map to Dolibarr users. We extract the SAP user ID, email, first name, and last name from USR02/BAGR. The SAP user type (dialog, system, communication) determines whether a Dolibarr internal user or external user is provisioned. SAP role assignments (AGR_USERS) are preserved in a migration note because Dolibarr's permission model (PERMS) is structured differently. The customer's admin rebuilds role-based permissions in Dolibarr's home / admin / rights.php based on the exported SAP role inventory.