Migrate from Tranquil ERP to Acumatica

Tranquil customer records map directly to Acumatica Customers. The Acumatica Customer record holds billing address, contact information, and payment terms. Tranquil's Customer Connect group assignments are preserved as a custom text field (CustomerConnectGroup__c) on the Acumatica Customer screen. Active vs. inactive status from Tranquil maps to the Customer Status field.

Tranquil supplier records map 1:1 to Acumatica Vendors. The Vendor screen stores the primary contact, payment terms, and Remit‑to address, and can also hold the vendor tax ID and 1099 flag. Supplier transaction history from Tranquil is preserved by populating the original document reference fields (Vendor Ref and Source Doc) on Acumatica’s Bills and Adjustments screens, allowing auditors to trace each payable back to its Tranquil origin without manual lookup.

Tranquil items with serial/batch/expiry tracking map to Acumatica Stock Items with Lot/Serial classes assigned. Multi-UoM items from Tranquil require Acumatica's Sales Unit and Stock Unit split configuration — Tranquil's base UoM becomes Acumatica's stock unit, and the Tranquil alternate UoM becomes the sales unit with a conversion factor.

Tranquil sales orders map to Acumatica Sales Orders with line items referencing the migrated Stock Item IDs. Tranquil's order status (Open, Completed, Cancelled) maps to Acumatica's Order Status picklist. Because Acumatica holds order lines with separate shipment and invoice steps, Tranquil fully invoiced orders migrate as Completed with no further action required.

Tranquil's single-step PO (which both orders and receives inventory) must be decomposed into two Acumatica records: a Purchase Order for the commitment and a Purchase Receipt for the goods-in action. Tranquil's received quantity and received date are used to pre-populate the Acumatica Receipt. Lines with zero receipts become open Acumatica POs; fully received lines become Receipts linked to the PO.

Tranquil's flat chart of accounts maps to Acumatica's account structure with branch scoping. Each Tranquil cost center that has independent financial reporting needs a corresponding Acumatica Branch record; Tranquil GL codes become Acumatica accounts grouped under the branch. This is the most complex mapping step because branch-to-GL alignment affects every AP, AR, and inventory posting.

Tranquil's open AR invoices map to Acumatica Customer Invoices, preserving the original invoice number in the Reference Nbr field for audit traceability. Each invoice retains its due date, terms, and amount. Tranquil payment records become Acumatica Payments; during import each payment is applied to the matching invoice via the Application tab, keeping the same open balance and aging, while any over‑payment creates a credit that can be released manually.

Tranquil's open AP bills map to Acumatica Vendor Bills, storing the original vendor invoice number in the Vendor Ref field for traceability. Each bill keeps its invoice date, due date, and amount. Tranquil AP payment records become Acumatica Payments; during import each payment is applied to the matching bill via the Application tab, preserving the open balance and aging, while any over‑payment creates a credit the AP team can release.

Tranquil's inventory adjustment records—created during cycle counts, write‑downs, or scrap—map to Acumatica Inventory Adjustments, storing the original reason in the Reference Nbr field or a custom Reason field for reporting. The adjustment date, quantity changed, and cost impact are carried over as they appear in Tranquil, keeping the inventory ledger consistent. Any batch or serial numbers are recorded on the Lot/Serial Detail screen, preserving traceability.

Tranquil's task records map to Acumatica Activities linked to the relevant Customer or Project. Tranquil's assigned-to employee maps to the Acumatica Owner field via email match against Acumatica users. Original due date and completion date from Tranquil are preserved on the Activity.

Tranquil employee records map to Acumatica Employees, transferring name, email, and department into the Acumatica employee screen. The cost‑per‑sale figure is saved as a custom numeric field (TranquilCostPerSale__c) for reporting continuity. Active or inactive status is carried forward, and any Tranquil role such as salesperson or purchase manager is noted in a custom Role__c field for the Acumatica admin to map to security roles.

Every Tranquil custom property (any field added outside the base schema on Customers, Items, Suppliers, Orders, or Employees) requires an Acumatica custom field defined in a Customization Project. The field data migrates into these new custom fields after the project is published. Tranquil field data types are translated to the closest Acumatica field type (text → string, number → integer or decimal, date → date).