Migrate from CREST ERP to Acumatica

CREST stores customer name, primary contact, and primary address in one record. Acumatica splits this into a Customer entity (business name, billing address, tax registration) and a Contact entity (individual name, email, phone, roles). We split CREST records into paired Customer + primary Contact entities, map additional CREST contact rows to secondary Contact records linked by CustomerID, and preserve the primary-contact flag as a custom field (IsPrimaryContact__c) for reference.

Direct 1:1 mapping for vendor header data. CREST vendor fields (name, tax ID, payment terms, credit limit) map to Acumatica Vendor fields. CREST vendor contacts migrate as Acumatica Vendor contacts linked by VendorID. Payment terms require value mapping — CREST's terms codes translate to Acumatica payment term codes (e.g., 'NET30' → '30 DAYS').

CREST inventory items carry item code, description, UOM, item type, cost method, reorder point, and warehouse assignment. All map directly to Acumatica Stock Item fields. CREST warehouses must be pre-mapped to Acumatica SiteIDs — each SiteID belongs to a Branch, and orphan site assignments block inventory transactions in Acumatica. UOM names are mapped value-by-value; non-matching UOMs are flagged for Acumatica administration before the import runs.

Order headers map directly: order number → OrderNbr, order date → Date, customer reference → ExternalRef, status → Status. Line items map with line number preservation. CREST's SalesRepID resolves by email match to Acumatica SalespersonIDs — unmatched owners are flagged before migration. Open orders migrate as open; completed orders migrate as historical records linked to the original invoice or shipment.

PO header maps 1:1: PO number → OrderNbr, date → Date, vendor → VendorID, buyer → extracted from CREST Buyer field and mapped to a note or custom field (CREST Buyer has no direct Acumatica equivalent in standard PO). Line items map with line number preservation. Open POs migrate as open; received POs migrate with receipt history as GL batches.

CREST project header maps to Acumatica Project: project number → ProjectID, project name → Description, status → Active (value-mapped), manager → OwnerID (email-matched). CREST sub-projects and tasks map to Acumatica project tasks. CREST project templates have no Acumatica equivalent — we export the template structure as a reference document for manual rebuild in Acumatica Project Accounting.

CREST's flat chart of accounts must be restructured into Acumatica's dimensional GL. Each CREST account maps to an Acumatica Account record; the CREST CostCenter or Department field maps to an Acumatica Subaccount. Before migration, your Acumatica admin must define the Branch (legal entity or operating unit) that owns each account-subaccount combination. We deliver a branch-and-subaccount setup plan based on your CREST account and cost-center values.

CREST asset records map to Acumatica Fixed Asset: asset code → AssetTag, description → Description, type → ClassID (value-mapped), acquired date → AcquisitionDate, useful life → UsefulLife, original cost → AcquisitionCost, depreciation method → DepreciationMethod (value-mapped: CREST 'straight-line' → Acumatica 'Straight-Line'). Asset depreciation schedules are not migrated — Acumatica calculates them from acquisition date and method at go-live.

CREST HRMS data (employee records, payroll, leave management) does not map to Acumatica's standard Employee module without significant setup — Acumatica Human Resources requires its own configuration for pay grades, accrual balances, and org structure. We export CREST employee records as a CSV for import into Acumatica HR or a third-party payroll system, flagged for manual review.

CREST custom objects and custom fields without a direct Acumatica equivalent are exported as reference data and mapped to Acumatica custom fields or generic inquiry tables. We surface every CREST custom field during the assessment phase and decide per-field whether to create an Acumatica custom field, store the data as a generic inquiry, or preserve it as a CSV reference.