Migrate from Xentral ERP to Epicor Prophet 21

Xentral stores address records as a unified Address object used for both customers and vendors. We split this into Epicor Customer (with ShipTo and BillTo records) and Supplier (Vendor) records at migration time using an address-type flag we detect during the Xentral export. Custom Address fields on Xentral migrate to Customer UD fields. Tax ID and payment terms transfer to Epicor Customer.TaxRegionID and Terms logic. German VAT IDs map to Epicor's Tax Connect region codes for EU-compliant invoicing.

Xentral Articles map directly to Epicor Part records. We preserve the Article number as Part.PartNum, multilingual labels as PartDtl records, and Article-specific pricing rules as Epicor PricePerQty records. Article categories map to Part.UnitPrice and Product Group codes. Xentral's variant/article combination structure (if used for product variants) maps to Epicor's PartRev configuration where BOMs exist. Custom fields on Articles migrate to Part UD fields.

Xentral Sales Orders map to Epicor OrderHed (header) and OrderDtl (line) records. The Xentral order number preserves as OrderHed.OrderNum reference. Order status maps to Epicor OrderRel.OpenRelease logic. Shipping warehouse and carrier assignment transfer from Xentral's logistics fields. Line item quantities and pricing migrate as OrderDtl with the resolved Part.PartNum reference. Xentral order dates become Epicor OrderDtl.ReqDate.

Xentral Purchase Orders map to Epicor POHeader and PODetail records. The Xentral po_number preserves as POHeader.PONum. Vendor assignment resolves to the Epicor Supplier record created from the corresponding Xentral vendor Address. Expected delivery dates, received quantities, and outstanding PO balances migrate to PODetail with OpenRelease tracking in Epicor's PORel table.

Xentral outgoing invoices (AR) map to Epicor InvcHead and InvcDtl records. Document numbers and dates preserve. Gross, net, and tax amounts map to Epicor's currency fields with exchange-rate context from the original Xentral multi-currency setup. Xentral payment terms map to Epicor Terms. We flag any invoices with partial payments for manual reconciliation against Epicor's payment application records.

Xentral incoming invoices (AP) map to Epicor APInvoice records with Vendor and GLAccount assignments. Tax amounts require mapping from the German VAT/Swiss VAT system used in Xentral to Epicor's Tax Connect country codes and tax jurisdiction logic. We flag any AP invoices that reference non-migrated purchase orders so that matching can occur post-migration.

Xentral warehouse records map to Epicor Warehse (warehouse definition) and PartBin (stock levels per part per warehouse per bin). Batch and serial numbers from Xentral's inventory tracking migrate to PartBin with lot traceability records in Epicor's PartLot table. Stock snapshots require a data freeze period during migration because real-time stock levels shift continuously. We coordinate a migration window with the customer to capture a stable inventory state and reload bin-level quantities after Epicor go-live.

Xentral Projects map to Epicor Project records when Epicor Project Billing or Project Management modules are in scope. Project-linked orders and invoices from Xentral associate to the Epicor Project via OrderHed.ProjectID and InvcHead.ProjectID. Custom fields on Xentral Projects migrate to Project UD fields. We note that project-level task dependencies and time entries require separate scoping because Epicor's project task structure is hierarchical and differs from Xentral's flat task list.

Xentral's chart of accounts, journal entries, and cost centres map to Epicor GL Account and Cost Centre records. However, German and EU tax codes, VAT configurations, and DACH-region legal entity requirements do not map directly to US-centric Epicor tax structures. We export account codes and names and flag every account requiring manual cost-centre assignment or tax jurisdiction mapping in Epicor GL. Bank account connections require re-establishment in Epicor's Treasury module post-migration.

Xentral custom fields on Articles, Addresses, and Projects migrate to Epicor UD fields on the corresponding Part, Customer, or Project record. We create the UD field definitions in Epicor's Customization Editor before import. Fields that do not have a natural Epicor equivalent (for example, Xentral-specific integration flags) are preserved as text UD fields and documented for the customer's admin to decide whether to retain, consolidate, or retire post-migration.

Xentral delivery notes (shipping documents tied to sales orders) map to Epicor ShipHead and ShipDtl records linked to the migrated OrderDtl. Credit memos map to InvcHead with negative amounts and a credit memo flag. The parent order relationship is preserved via OrderNum reference. We document any Xentral delivery notes that were issued against orders not yet migrated so that the customer's team can manually close the order relationship in Epicor.

File attachments linked to orders, articles, and addresses in Xentral are downloaded via the API and re-uploaded to the Epicor Document Management system (EDMS) or an attached external file store (SharePoint, S3). We preserve the original filename and the record association (OrderHed, Part, or Customer reference) so that users can retrieve attachments from the Epicor context panel post-migration. PDF attachments for invoices and delivery notes are stored separately and linked to the corresponding document record.

Xentral Flows workflows are automation rules stored in the Xentral Connect middleware layer and are not accessible through the Xentral REST API. We cannot export workflow definitions programmatically. During discovery, we audit active workflows by reviewing Xentral Connect execution logs and document each workflow's trigger, conditions, and actions. We deliver a written inventory with a recommended Epicor Kinetic BPM or REST adapter equivalent for each workflow. The customer's Epicor implementation partner or internal admin rebuilds the automations post-migration.