Migrate from Sage Business Cloud X3 to Infor CloudSuite Corporate

X3 Business Partners are the unified third-party entity spanning customers and suppliers. We map to Infor's Customer and Supplier master records, preserving BP category codes, address hierarchies, payment terms, currency settings, and credit limits. X3 BP templates (e.g., for flat-file export) must be configured to expose all address and contact fields before extraction. Custom fields on BP records migrate to Infor Extended Properties via the Import Rule Definition form.

X3 Sales Orders exported via template ZSOH include order header, lines, delivery addresses, pricing, taxes, and discounts. We map order status lifecycle (draft, confirmed, shipped, invoiced) to Infor's order state model. The X3 order number becomes the Infor Customer PO number; Infor generates its own Sales Order number during import. Historical orders with open status require open-line reconciliation against Infor's shipment and invoice tables.

X3 Purchase Orders map to Infor Purchase Orders with commitments, receiving links, and approval workflow status preserved as custom fields. X3's multi-site PO capability (PO linked to a specific site for receiving) maps to Infor's site-specific PO routing. Approval workflow states do not migrate as active workflows; we deliver a written list of PO approval thresholds for the Infor admin to reconfigure in Infor Process Designer.

X3's hierarchical, segment-coded chart of accounts with cost centers and dimensions per company code maps to Infor's dimensional GL structure. Each X3 company code becomes an Infor legal entity. We extract the full account hierarchy including account type, posting definitions, and multi-currency settings. X3's multi-ledger capability (different accounting representations per entity) maps to Infor's ledger definition per legal entity. Intercompany account mappings require explicit mapping between X3 company codes and Infor legal entity IDs.

X3 AP and AR modules linked to Business Partners export open invoices, credit limits, payment terms, and aging data via templates. We map open AP/AR invoices to Infor AP/AR records with payment terms, due dates, and aging buckets preserved. X3's multi-currency invoice handling (exchange rates per transaction date) maps to Infor's multi-currency AP/AR with the original transaction currency and rate stored. Historical paid invoices migrate as closed records with full payment history.

X3 Fixed Assets carry acquisition cost, depreciation schedules, and multiple parallel depreciation books (GAAP, tax, statutory) with independent methods per legislation. We extract all active depreciation books with their conventions (straight-line, declining balance, units of production) and map to Infor's Fixed Assets with parallel book definitions. Asset tags, locations, and asset groupings migrate as custom fields or Infor asset categories. Accumulated depreciation per book migrates to Infor's book-level accumulated depreciation fields.

X3 supports multiple depreciation books per asset with different methods and conventions per legislation. Infor similarly supports multiple depreciation books per asset. We extract the full book matrix (asset ID, book ID, method, convention, useful life, residual value, accumulated depreciation) and configure matching Infor depreciation book definitions before asset migration. The migration utility uses SourceDL_FixedAsset_ImportSp and TargetDL_FixedAsset_ImportSp patterns with import rules for currency conversion on acquired foreign assets.

X3 Products with Bills of Materials, routings, lot/serial tracking, expiry dates, and multi-site stock levels map to Infor's Item Master. Site-level stock quantities map to Infor warehouse inventory records. Lot and serial numbers migrate as inventory attributes. BOM and routing links are extracted as separate objects (see Production Orders note) because X3 does not store the BOM-routing association as a direct foreign key, requiring re-linkage in Infor.

X3 Production Orders with BOMs, routings, work centres, and component consumption map to Infor Work Orders. The critical migration risk is that X3 does not store the BOM-routing relationship as a direct foreign key—it derives it at runtime from the production order parameters. We extract BOM and routing definitions as separate objects, then re-link them to Infor Work Orders using Infor's BOM-Routing assignment workflow post-migration. We deliver a written BOM-Routing mapping table for the Infor admin to resolve manually during configuration.

X3 Budgets and Commitments tied to the GL spanning multiple periods and scenarios map to Infor's budget and commitment records. Commitments representing purchase orders not yet posted map to Infor as open PO commitments with budget impact flags. We extract scenario definitions (e.g., Actual, Budget, Forecast) and map them to Infor financial scenarios with period mappings preserved.

X3 user management with role-based function-level permissions per site and company maps to Infor's user and role architecture. X3 named-user IDs (non-email-based in older deployments) must be mapped to Infor user accounts, which use the Infor OS identity layer. We preserve X3 function-level permission sets as Infor roles, flagging any permissions that require Infor-specific configuration beyond the standard role definition. Orphaned permissions (X3 users without a clear Infor equivalent) are flagged for manual review.

X3 custom fields on business objects (stored as extended columns in the underlying table) migrate to Infor Extended Properties via the Import Rule Definition form. We detect all custom fields during data profiling, map their data types to Infor field types, and configure import rules for any type conversions (e.g., X3 checkbox Y/N to Infor 1/0). Custom fields on non-standard X3 dictionary objects require Infor Consulting Services for custom stored procedure creation if the migration utility's predefined stored procedures do not cover the source table.