Migrate your Sage Business Cloud X3 data

Business Partners are the core third-party entity in X3, spanning both customers and suppliers. The Import/Export template system exposes all standard fields including address, payment terms, currency, tax information, and custom fields. We migrate Business Partners 1:1 and map the BP category (customer vs. supplier vs. both) to the destination's equivalent object.

Sales Orders are managed via template 'ZSOH' for flat-file export. X3 stores order header, lines, delivery addresses, pricing, taxes, and discounts. We preserve the full order lifecycle including status and linkages to Invoices and Deliveries. Open orders are migrated with status flags; closed orders are migrated as historical records.

Purchase Orders mirror the Sales Order structure but for procurement. X3 supports commitments, receiving links, and approval workflows. We map Purchase Orders to the destination's equivalent PO object, preserving line-level detail, delivery schedules, and intercompany routing where applicable.

X3 uses a hierarchical, multi-ledger chart of accounts supporting segment codes, cost centers, and dimensions. Accounts are tagged per company code and can carry multi-currency settings. We extract the full account structure and map it to the destination's COA, flagging any accounts that require dimension expansion.

X3 stores AP and AR as separate modules linked to Business Partners. Open invoices, credit limits, payment terms, and aging data are exported via templates. We map open AP/AR to the destination's vendor/customer ledger, applying the correct aging buckets and payment term logic. Closed invoices are migrated as historical records.

Fixed Assets in X3 include acquisition cost, depreciation schedules, asset registers, and tax-book depreciation per legislation. The Fixed Assets module supports multiple depreciation methods and asset revaluation. We map asset registers including accumulated depreciation, useful life, and disposal history.

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, Stock levels, Locations, and Lot/Serial numbers, but BOM explosion requires decision on whether to migrate as finished goods or exploded components depending on the destination schema.

Production Orders in X3 link to BOMs, routings, work centres, and consumption tracking. We map Work Order headers, operations, and component consumption, but the BOM-routing relationship must be reconstructed at the destination. Scheduling and capacity data are migrated as read-only historical records.

X3 supports parallel depreciation books per asset (e.g., GAAP book vs. tax book vs. local statutory book). Each book can have its own depreciation method and convention. We extract all active depreciation books and map them to the destination's equivalent, flagging any that require period-alignment adjustments.

Budgets and Commitments in X3 are tied to the GL and can span multiple periods and scenarios. Commitments represent purchase orders or contracts that haven't yet posted. We map commitment records as budget reservations or pre-encumbrances in the destination, preserving amounts, periods, and departments.

X3 user management includes Role-based access control with function-level permissions per site and company. Users are named (not email-based in older deployments). We map Users to the destination's user object, preserving role assignments and site access, but custom permission sets require manual review post-migration.

X3 supports custom fields on most business objects via its data dictionary. These are stored as extended columns in the underlying table. We detect and export all custom fields, map them to the destination's equivalent custom field mechanism, and flag any that cannot be represented in the target schema.