Migrate from Xentral ERP to Infor CloudSuite Corporate

Xentral stores address records as a unified Address object covering both customers and vendors. We split on the Xentral address_type or role field: Customer addresses map to Infor Business Partner with Role = Customer, and vendor addresses map to Infor Business Partner with Role = Supplier. Tax IDs migrate to Infor's Tax ID fields on the Business Partner. Custom Address fields from Xentral (configured in System Settings) transfer to Infor Business Partner extension fields. The Infor migration utility requires Business Partner records to exist before Purchase Orders or Sales Orders can be imported, so this is the first object we migrate.

Xentral Articles map to Infor Product records. The Xentral article_number becomes the Infor Product Code, serving as the dedupe key during import. Multilingual article labels from Xentral transfer to Infor Product descriptions for each configured language. Xentral custom fields on Articles (such as hs_code, country of origin, or unit of measure variants) migrate to Infor Product extension fields. Item-specific pricing rules require manual review against Infor's Price List configuration post-migration.

Xentral Sales Orders map directly to Infor Sales Order records with the order number preserved as xo_number or equivalent. The order date, assigned warehouse, and shipping information transfer directly. Line items resolve to the Infor Product records created from Xentral Articles. The Xentral order status (open, invoiced, cancelled) maps to the corresponding Infor Sales Order status. Infor requires Business Partner and Product records to exist before Sales Order import, so this runs third in the dependency sequence.

Xentral Purchase Orders map to Infor Purchase Order records with po_number and creation date preserved. Vendor assignment resolves to the Infor Business Partner (Supplier role) created from the Xentral vendor address. Expected delivery dates and received quantities transfer directly. Open and closed PO records migrate; closed POs transfer with their received quantity history intact. This runs after Business Partner and Product import, in parallel with Sales Order migration.

Xentral generates both accounts receivable and accounts payable invoices as separate document objects. We map AR invoices to Infor's accounts receivable billing records linked to the Sales Order (if order-linked) or the Business Partner (Customer). AP invoices map to Infor's accounts payable records linked to the Purchase Order or Business Partner (Supplier). Multi-currency invoices require exchange rate mapping: we extract the Xentral exchange rate applied at invoice creation and apply the equivalent rate configuration in Infor during import. The Infor migration utility requires chart of accounts and tax codes to be configured before invoice import.

Xentral stock levels, warehouse assignments, and batch/serial information stored per Article map to Infor Stock records per warehouse location. We perform a point-in-time stock snapshot during a freeze period to capture accurate levels. Batch tracking fields vary by warehouse configuration in Xentral; we map batch_number, expiry_date, and serial_number fields to the corresponding Infor Stock attributes. Real-time stock during migration requires a freeze window agreed with the customer to avoid data drift.

Xentral's accounting module stores the chart of accounts, journal entries, and bank account connections. We map account codes and names from Xentral to Infor GL Account records. Tax code configurations and cost centre assignments require manual review and entry in Infor forms before financial data import because the Infor migration utility requires prerequisite accounting structures to exist. Multi-entity consolidation structures in Xentral map to Infor's legal entity configuration. We do not migrate bank connection credentials; these must be reconfigured in Infor post-migration.

Xentral Projects map to Infor Project records with project code, name, status, and dates preserved. Custom fields on Xentral Projects transfer to Infor Project extension fields. Project-linked orders and invoices reference the migrated order and invoice IDs. Task dependencies and time entries stored within Xentral Projects require separate manual mapping or a time-tracking reconfiguration in Infor because the Infor project task model differs structurally from Xentral's.

Xentral custom fields are supported only on Articles, Addresses, and Projects. We export the custom field values as properties and flag any that cannot map to typed Infor fields (for example, Xentral workarounds for Orders or Invoices). The field definitions themselves require manual re-creation in Infor CloudSuite as extension fields or user-defined fields before values can be imported. We provide a custom field inventory document listing each Xentral custom field, its type, the object it attaches to, and the recommended Infor field type for the customer's admin to configure pre-import.

Xentral delivery notes and credit memos are document-type objects tied to parent Sales Orders or Invoices. We preserve the document hierarchy during migration, mapping Xentral delivery_note_number to the equivalent Infor sales document reference. Credit memos map to Infor Credit Memo records linked to the original invoice. PDF document attachments are exported separately from database records and re-uploaded to Infor Document Management (IDM) with the parent record association preserved.

Xentral Flows workflows are automation rules stored in the Xentral Connect middleware layer and are not accessible through the Xentral REST API. We cannot extract workflow definitions programmatically. During discovery, we audit active workflows by reviewing Xentral Connect execution logs and document each workflow's trigger (event or schedule), conditions, and actions. This inventory is delivered as a written handoff document. The customer's Infor implementation team rebuilds these in Infor OS Ming.le workflow designer or the relevant CloudSuite process automation layer post-migration.