Migrate from Sage Business Cloud X3 to Microsoft Dynamics 365 Business Central

X3 Business Partners cover both customers and suppliers in a single entity with a BP Type flag. We split them at migration time into Dynamics 365 Customer and Vendor records. Address handling requires restructuring: X3 allows multiple independent address records with separate invoice and delivery roles; Dynamics 365 stores a single address table where each address can carry multiple roles (Invoice To, Ship To, Primary), and only one address can be marked primary per Business Unit. We pre-process address records to collapse X3's multiple address structures into Dynamics 365's role-based model before import.

X3 uses a hierarchical COA with segment codes, cost centers, and per-company assignments supporting multi-currency and multi-legislation. Dynamics 365 Finance and Operations uses a flat Main Account structure with Financial Dimensions (dept, division, project, site, customer, vendor) that replicate the segmentation behavior. We extract X3's account hierarchy and segment values, map them to the destination's Main Account structure and active Financial Dimension set, and configure the dimension-based posting rules before the GL import begins.

Historical GL journal lines migrate as General Journal entries in Dynamics 365. We preserve the original posting date, journal batch number, account and dimension assignments, debit/credit amounts, and currency. X3's multi-company journal entries require splitting per legal entity: a journal affecting accounts in two X3 companies becomes separate journal lines in corresponding Dynamics 365 legal entities. Period-end closing flags and reversing entries are captured and reproduced in the destination.

X3 requires manual duplicate entry of intercompany JVs per legal entity rather than auto-generating balanced counterparty entries. We identify intercompany GL entries by analyzing account assignments across X3 company codes, then reconstruct them in Dynamics 365's intercompany journal framework, which generates balanced counterpart entries automatically. This is one of the highest-value migrations for multi-entity X3 customers because it eliminates the manual duplication going forward.

Open AP and AR invoices, credit limits, payment terms, and aging data export from X3 via AP/AR templates. We map open invoices to Dynamics 365 Vendor Invoice and Customer Invoice records, preserving invoice number, posting date, due date, currency, tax information, and the Business Partner reference. Historical paid invoices migrate as posted journal lines rather than open records. Payment terms and credit limits map to Dynamics 365 Vendor and Customer terms and credit structures.

X3 Fixed Assets carry acquisition cost, depreciation schedules, asset registers, and tax-book depreciation per legislation. Dynamics 365 Finance and Operations Fixed Assets module supports parallel depreciation books, multiple depreciation methods (straight-line, declining balance, units of production), and tax-book integration. We extract all active depreciation books per asset, map them to the destination's Fixed Asset book structure, and preserve acquisition date, useful life, depreciation convention, and accumulated depreciation balance at cutover date.

X3 supports parallel depreciation books per asset (GAAP book, tax book, local statutory book) each with independent depreciation method and convention. We split these into separate Dynamics 365 Fixed Asset Book records under the same parent asset, preserving the per-book depreciation method, convention, and life. The accumulated depreciation balance at cutover date migrates per book, not rolled up to a single figure.

X3 tracks inventory at site level with multi-location support. Products carry Bills of Materials, routings, lot/serial tracking, and expiry dates. We map Products to Dynamics 365 Released Products with the appropriate product type (item, service, bom), copy BOM and routing structures where applicable, and map stock levels by site to warehouse locations. Lot and serial number tracking settings migrate as inventory dimension groups.

X3 Sales Orders export via template ZSOH for flat-file extraction, covering order header, lines, delivery addresses, pricing, taxes, and discounts. We preserve the full order lifecycle including status, open quantities, and delivery schedule. Orders with a status of Delivered or Invoiced migrate as historical records; open orders migrate as active records in Dynamics 365 with remaining quantities and delivery addresses.

X3 Purchase Orders mirror the Sales Order structure but for procurement, supporting commitments, receiving links, and approval workflows. We map open Purchase Orders to Dynamics 365 Purchase Orders with line quantities, delivery dates, and vendor references. Acknowledged quantities and receiving links are preserved where available. Closed or invoiced POs migrate as historical records.

X3 Production Orders link to BOMs, routings, work centres, and consumption tracking for both process and discrete manufacturing. We map Work Order headers, operations, and component consumption. Note that the BOM-routing relationship must be reconstructed in the destination because routing assignments are relationship-based in both systems; we extract routing references and recreate them during the BOM and routing setup phase before work orders import.

X3 Budgets and Commitments tie to the GL and span multiple periods and scenarios. Commitments represent purchase orders or contracts not yet posted. We map budget amounts as Budget Register Entries in Dynamics 365 Finance and Operations with the corresponding financial dimension combinations. Open commitments map as pre-encumbrance or posted encumbrance records linked to the relevant Purchase Orders.

X3 user management uses Role-based access control with function-level permissions per site and company. In many X3 deployments, particularly older or on-premise instances, user logins are named user IDs rather than email addresses. We map X3 user IDs to Azure AD-backed Dynamics 365 user accounts by email resolution where available or by creating new user accounts with matching role assignments. Orphaned permissions are flagged for manual remediation post-migration.

X3 supports custom fields on most business objects via its data dictionary, stored as extended columns in the underlying table. We detect and export all active custom fields, map them to Dynamics 365 extension fields (field extension or custom field depending on the destination edition), and validate the target field type compatibility. Custom field values migrate as part of the parent object import.