Migrate from iDempiere to Acumatica

iDempiere stores both customers and vendors in one C_BPartner table with IsCustomer and IsVendor flags. FlitStack splits these into separate Acumatica Customer and Vendor records, preserving BP-level fields (credit status, payment terms, tax ID) on both destinations and the original C_BPartner_ID as a reference field.

Each BP location becomes a separate Acumatica address record linked to the corresponding Customer or Vendor entity. iDempiere location address fields (Address1-5, City, Region, PostalCode, Country) map directly to Acumatica's address line fields, with country-specific validation rules applied from Acumatica's country configuration during import.

iDempiere's product type field (ProductType: Item vs Resource vs Service) determines the Acumatica Item Type. Items marked as stocked in iDempiere become Acumatica Stock Items with Warehouse Management; services and resources map to Non-Stock Items. The original M_Product_ID is preserved as ExtRefMProductID on the InventoryItem.

iDempiere's vendor-specific purchase pricing per product migrates to Acumatica's Vendor Inventory Item screen, keyed by VendorID and InventoryID. Current cost, vendor product ID, and lead time are preserved. If multiple vendors exist per product, all vendor price records are migrated.

iDempiere sales orders map to Acumatica Sales Orders with line items, taxes, discounts, and charges preserved. Order date, promised date, and warehouse-ship-from branch are migrated. Status (Draft, In Progress, Completed, Voided) maps to Acumatica's order status field. The original document number becomes ExtRefCOrderID.

iDempiere purchase orders migrate to Acumatica Purchase Orders with vendor, date, and line items intact. Drop-ship flags and receipt warehouse assignments are preserved as branch and warehouse references. POLine tax amounts are recalculated using Acumatica's tax zone for the vendor country.

Acumatica requires a valid AccountID and BranchID on every journal line — iDempiere GL lines are scanned and unmatched account codes are flagged before migration. Dimensional segments (Business Partner, Product, Project, Campaign) map to Acumatica's segment keys defined on the Chart of Accounts. Post date and fiscal period are validated against Acumatica's period status.

iDempiere supports multiple parallel accounting schemas per tenant. Each schema's account structure becomes a separate Chart of Accounts in Acumatica, or branches within a single company are used if Acumatica's multi-company intercompany accounting is not required. The schema's currency and cost precision are applied to the company setup.

iDempiere document number sequences use pattern strings with current next numbers. Acumatica validates sequence format against a mask (digits, letters, prefix/suffix). Sequences with custom patterns that do not fit Acumatica's mask are flagged — FlitStack creates a valid Acumatica sequence and logs the original sequence name and last used number for reference.

iDempiere's flat multi-org model (all organizations share one DB catalog) maps to Acumatica's multi-company or branch-per-org model. Each iDempiere AD_Org becomes either a separate Acumatica Company (for distinct legal entities) or a Branch within an Acumatica Company (for operational divisions). The mapping plan is built before migration so organizational data lands in the correct tenant.

iDempiere file attachments stored in the database or on the file system are extracted and re-uploaded to Acumatica's Files screen, associated with the parent entity (Customer, Vendor, Sales Order, etc.) by record reference. File size limits per Acumatica attachment configuration apply.