Migrate from Adm Cloud to Acumatica

Adm Cloud customers map 1:1 to Acumatica Customers. Acumatica supports multiple addresses (billing/shipping) and multiple contacts per customer — the primary contact becomes the primary, others become secondary Contact records linked via the Relations tab. Customer class maps to Acumatica's Customer Class for AR account defaults.

Adm Cloud vendors map to Acumatica Vendors. Acumatica adds vendor-specific attributes: Tax Zone assignment for 1099/non-1099 reporting, Remittance Address separate from Main Address, and Payment Method preference. These are populated from Adm Cloud's vendor record or set to defaults if the source data doesn't carry them.

Adm Cloud items tagged as 'stocked' split to Acumatica Stock Items with lot/serial and warehouse tracking enabled. Non-stocked items in Adm Cloud become Acumatica Non-Stock Items without warehouse quantity. The split is driven by Adm Cloud's inventory-type flag — if that flag is absent, items default to Non-Stock and your admin reclassifies any that need warehouse tracking.

Adm Cloud's flat account codes map to Acumatica accounts with the first subaccount dimension carrying Adm Cloud's cost-center or department code. If Adm Cloud uses only a flat chart, the subaccount dimension is left null. Acumatica's active/pending/posting status is set to Active for all migrated accounts — your accountant confirms posting eligibility.

Open Sales Orders migrate with all line items, quantities, and scheduled ship dates. Acumatica requires a Branch and Warehouse assignment on each order line — these default from the customer's default shipping address unless your Adm Cloud data carries an explicit warehouse reference. Completed orders migrate as order history for reporting continuity.

Open Purchase Orders migrate with vendor, line items, expected receipts, and land cost allocations. Acumatica requires a Branch assignment on POs. Landed costs (freight, duty, insurance) defined in Adm Cloud become separate Landed Cost Codes in Acumatica linked to the PO receipt.

Unpaid AR Invoices migrate with original invoice date, due date, terms, and open balance preserved as an AR Invoice in Acumatica. Payments received but not yet applied in Adm Cloud are migrated as unallocated payments and auto-matched during the delta pickup. Paid invoices migrate as historical records for aging-report continuity.

Unpaid AP Invoices migrate with original invoice date, due date, terms, and open balance. Acumatica's Bill variant is used for accrual-mode invoices. Prepayments and credit memos migrate as separate AP documents linked to the vendor — your AP team applies them in Acumatica post-migration.

Adm Cloud AR payments map to Acumatica Payments allocated against the migrated AR Invoice. If the original invoice was not migrated (fully paid), the payment migrates as an unallocated payment against the customer. Original payment method (check, ACH, credit card) is stored in a custom note.

Adm Cloud shipments map to Acumatica Shipments linked to the corresponding Sales Order. Lot/serial numbers assigned in Adm Cloud are recorded in Acumatica's lot/serial tracking fields if the inventory item is lot-tracked. Carrier and tracking information migrates to the Shipment's external reference field.

Adm Cloud support cases migrate to Acumatica Cases with original creation date, assigned user, status, resolution summary, and related customer. Open cases land as Open in Acumatica; closed cases land as Closed with the resolution note preserved. Cases linked to inventory items carry the ItemID for reference.

Adm Cloud custom properties on any object (customer, vendor, item, order) are enumerated and mapped to Acumatica custom fields using the Usr prefix convention. Each custom field gets a corresponding custom field definition exported as a setup plan your Acumatica admin creates before the migration run. Field types are matched: text to string, numbers to decimal/integer, pick-lists to combo boxes.

Adm Cloud tax codes map to Acumatica Tax Zones per jurisdiction (state/province/country) and Tax Categories per item class. Multi-jurisdiction tax codes in Adm Cloud split into multiple Acumatica Tax Zone records with the same effective rate. Your tax advisor reviews the mapping for accuracy before activation.

Adm Cloud warehouse and location records map directly to Acumatica Warehouses in a one-to-one relationship. Each warehouse receives a default Branch assignment during migration — if Adm Cloud doesn't carry branch reference data, all warehouses default to the primary branch and your Acumatica admin reassigns them post-migration using the branch-to-warehouse mapping table provided in the migration package.

If Adm Cloud carries multiple company entities or divisions, each maps to an Acumatica Branch. Branches in Acumatica are legal entities for financial reporting; each has its own AP/AR subledger and can run consolidated reports. Single-company Adm Cloud setups create one primary Branch in Acumatica.