Migrate from Xentral ERP to Acumatica

Xentral stores customer and company data in its Address (Adresse) entity — includes billing/shipping address, tax ID, payment terms, and credit limits. Direct map to Acumatica Customer. Acumatica requires a Customer Class to be assigned; we map Xentral's customer type flag to the nearest Acumatica Customer Class. If Xentral stores both a company and individual contacts under the same address record, we split into one Customer and one Contact in Acumatica.

Xentral Articles serve as the universal product entity for both stocked and non-stocked items. We split by Xentral's inventory tracking flag: items with warehouse-bin assignment and BOM structures map to Acumatica Stock Item (with warehouse, lead times, and BOM data); items defined as service, digital, or drop-ship map to Acumatica Non-Stock Item. The split requires a source-field lookup before import so each record goes to the correct Acumatica entity type.

Xentral Sales Orders map directly to Acumatica Sales Orders — header fields (order number, customer reference, dates, terms) and line items (article, quantity, unit price, discount) transfer as-is. Xentral's order-status values (open, invoiced, shipped) map to Acumatica's status field. Shipment and invoice documents in Xentral are separate related records; we map them to Acumatica Shipment and AR Invoice documents linked by the original order reference.

Xentral Purchase Orders map to Acumatica Purchase Orders with the same line-item structure — vendor reference, line items, quantities, and costs. Xentral's vendor-address logic maps to Acumatica's Vendor record and Remit-to address. If Xentral tracks landed costs or duty per PO line, those map to Acumatica's Landed Cost item framework.

Xentral outgoing invoices (created from orders or standalone) map to Acumatica AR Invoice records. The invoice number from Xentral maps to Acumatica's Reference Nbr. field — we preserve the original Xentral invoice number as a custom reference field and in the Invoice Nbr field if Acumatica's number sequence allows alphanumeric values. Tax calculation logic from Xentral requires review since Acumatica uses a Tax Zone and Tax Category model for VAT/GST posting.

Xentral Projects map to Acumatica Projects — project name, dates, customer link, budget amounts, and status transfer directly. Xentral's project-task breakdown maps to Acumatica's Project Task entity. If Xentral stores time or expense records against projects, those map to Acumatica's Time Entry and Expense Receipt records under the corresponding Project Task.

Xentral warehouse definitions and bin locations map to Acumatica Warehouse and Warehouse Location entities. Bin-level tracking in Xentral (shelf, rack, position) maps to Acumatica's LocationID structure within each Warehouse. If Xentral tracks multiple warehouses, each gets its own Acumatica Warehouse record with the appropriate Branch assignment.

Xentral custom fields for Articles, Addresses, and Projects require an Acumatica Customization Project to define matching Usr-prefixed fields before data can import. We create the Customization Project XML (defining field type, label, and pick-list values) and apply it to the target Acumatica instance before import begins. The custom field definitions are the first artifact delivered in the migration plan so Acumatica admins can review and adjust before data lands.

Xentral file attachments on orders, articles, or addresses re-upload to Acumatica's Files and Attachments framework (NoteDoc records linked to the target entity). File size limits from Acumatica apply — files exceeding 25MB are flagged and split or linked externally. Inline images in Xentral notes are extracted and rehosted as NoteDoc records attached to the parent entity.

Xentral Flows automations — order routing rules, inventory threshold triggers, and CRM assignment logic — do not have an Acumatica equivalent that accepts a direct migration. We export the Xentral Flow definitions (trigger events, conditions, and actions) as a JSON configuration file that maps to Acumatica's Screen-Based Workflow screen or PowerScript logic. Your Acumatica implementation partner uses this export as a rebuild specification.

Xentral's native connector library (Shopify, Shopware, eBay, Amazon, DHL, PayPal) and Xentral Connect middleware do not migrate to Acumatica. Acumatica has its own ISV Marketplace (Shopify connector, eCommerce connectors) that must be reinstalled and reconfigured. We document each active Xentral integration endpoint, authentication method, and data sync direction as a configuration reference for rebuilding in Acumatica.

Xentral document templates (letterhead, invoice layout, packing slip formatting) are tied to Xentral's document designer and do not transfer to Acumatica's Report Designer. We export the template content (logos, field placements, term text) as a specification document that your Acumatica consultant uses to rebuild document templates in Acumatica's Report Designer.