Migrate from Embrace ERP to Acumatica

Embrace ERP account codes (e.g., 1000-001) map to Acumatica GL accounts by splitting the Embrace code into Acumatica segments. The full Embrace account code is preserved in Acumatica's NoteID and a custom AccountCode__c field for reconciliation and reference lookup after migration.

Embrace customer records map directly to Acumatica Business Accounts with Customer class. Primary contact, credit limit, payment terms, tax group, and address fields migrate as direct mappings. Customer hierarchies (parent/child) map to Acumatica's parent Account link. If Embrace stores multiple contacts per customer, secondary contacts migrate as related Contact records linked to the Business Account.

Embrace vendor records map to Acumatica Business Accounts with Vendor class. Payment terms, tax registration, bank details, and default GL accounts for AP expense mapping migrate directly. Multi-location vendor addresses map to Acumatica's Contact and Address tables per vendor. Default expense accounts from Embrace map to Acumatica's vendor-level AP expense account settings.

Embrace inventory items map to Acumatica Stock Items or Non-Stock Items based on the source item type. Unit of measure, item class, valuation method (Standard / Average / FIFO), and warehouse assignment migrate directly. Valuation details require Acumatica item class pre-configuration before records land.

Embrace warehouse and branch records map to Acumatica Branches. Each branch receives its own GL accounts for AP/AR and inventory subaccounts. Branch-to-Acumatica Branch mapping is required before customer, vendor, and inventory records can reference the correct branch ID. Acumatica's branch-specific configuration also controls tax zones, shipping methods, and reporting currencies per location.

Embrace open AR invoices migrate as Acumatica AR Invoices in draft or scheduled status. Line items (Product / Service) map to Invoice Details referencing the migrated Stock Item or Service. Tax amount, discount, and due date fields migrate as direct values. Posted invoices migrate as history not live records.

Embrace open AP bills migrate as Acumatica AP Bills in draft status. Vendor reference, invoice date, due date, and line amounts migrate directly. Taxes map via Acumatica's tax zone configuration per vendor. Prepaid and accrued invoice adjustments require manual review post-migration.

Embrace fixed asset records map to Acumatica Fixed Asset documents. Asset code, description, class, acquisition date, cost, residual value, depreciation method, and accumulated depreciation all migrate as direct fields. Asset depreciation schedules are recalculated in Acumatica based on the configured depreciation method.

Embrace open purchase orders migrate as Acumatica Purchase Orders in Open status. Vendor, shipment address, line items with quantities and unit costs, and promised dates migrate directly. Received quantities on partially-received POs are preserved so receiving against the PO can continue in Acumatica after go-live.

Embrace open sales orders migrate as Acumatica Sales Orders. Customer reference, ship-to address, line items with quantities and unit prices, and warehouse assignment migrate directly. Orders in fulfilment map to Acumatica's shipment workflow so picking and shipping can resume from the migrated state.

Embrace custom fields on Customer, Vendor, Inventory, and GL Account screens require manual creation as Acumatica Schema Extensions (DACs) — each custom field is recreated as a data access class field in the Acumatica Customization Project editor. Formula fields from Embrace do not migrate; Acumatica calculated fields or report Designer expressions replace them.

Embrace workflow definitions and approval routing rules have no Acumatica equivalent and cannot be migrated. They are documented as a rebuild scope advisory. Acumatica's Workflow Engine is configured independently per business process after data migration completes. We export each Embrace workflow as a process map showing triggers, approver levels, escalation paths, and conditions so Acumatica administrators can replicate the logic in the target system's screen-level and business-event-based workflow designers.