Migrate from Sage 300cloud to Acumatica

Sage 300cloud stores accounts as a single segment or combined code (e.g., 31000.001). We decompose this into an Acumatica Main Account (31000) and one or more Subaccount dimensions (001 = department, 002 = project, etc.) based on your Sage suffix conventions. Combination rules in Acumatica must be configured before accounts can be used in transactions.

Sage 300cloud customer records map directly to Acumatica Customer records. We preserve the customer ID, name, billing/shipping addresses, payment terms, credit limit, and Tax ID. Open AR invoices and credit memos load as separate AR transactions linked to the customer record.

Sage 300cloud vendor records map directly to the Acumatica Vendor screen. We transfer the vendor name, primary and secondary addresses, default payment terms, 1099 reporting flags, and Tax Registration ID. Open AP invoices and any debit memos load as distinct AP documents that reference the vendor record, preserving original invoice numbers, dates, and amounts for downstream reconciliation.

Sage 300cloud inventory items (stock and non-stock) map to Acumatica Inventory Items with item class assignments controlling valuation method (Standard, Average, FIFO). Lot/serial number histories and warehouse assignments are preserved. Landed-cost allocations (freight, duty, insurance) require Acumatica Landed Cost recalculation.

Open Sage 300cloud AR invoices are created as Acumatica AR Invoice documents, retaining the original invoice number, document date, due date, invoice amount, and line descriptions for reference. If full historical migration is requested, closed and paid invoices are imported as GL batches to maintain balance-forward continuity, ensuring that period totals in Acumatica match the Sage 300cloud ledger.

Open Sage 300cloud AP invoices are imported as Acumatica AP Invoice records, preserving the original vendor invoice number, invoice date, payment terms, and total amount on each line. Prepayments and credit memos are brought in as separate AP documents that link to the same vendor, maintaining the original references for accurate cash-application and aging reporting.

Open Sage 300cloud purchase orders are transferred to Acumatica as Purchase Order documents, carrying line items, ordered quantities, unit costs, and requested delivery schedules unchanged. Lines that have already been closed or fully fulfilled are imported as historical PO records for audit purposes, while received-but-not-invoiced lines generate receipt records in Acumatica that are linked back to the original PO, preserving traceability.

Open Sage 300cloud sales orders are mapped to Acumatica Sales Orders, preserving the original order number, order date, ship-by date, line items, and unit pricing. Orders that are linked to fulfillment generate shipment records in Acumatica upon release, and any lines that have already shipped in Sage are reflected as back-order quantities in Acumatica to ensure continuity of order-management reporting.

Sage 300cloud GL journal entries are imported as Acumatica Journal Transactions, retaining the original entry date, batch identifier, description, and each debit and credit amount. Entries that belong to multiple Sage companies are mapped to the appropriate intercompany journal configuration in Acumatica, and any adjusting entries created for year-end closes keep their original period reference to support accurate period-end reporting.

Sage 300cloud users who post transactions map to Acumatica Branches if your Sage setup uses company/department codes as posting dimensions. We resolve each Sage user by email to an Acumatica user account, then map their posting permissions to the appropriate Branch access.

Sage 300cloud user-defined fields on any entity require matching custom fields in Acumatica. We define Acumatica custom fields (or user-defined fields where applicable) during the schema preparation phase, preserving the source data type, default values, and pick-list options. For pick-list type fields, we build value-mapping tables that translate the Sage 300cloud codes to the corresponding Acumatica pick-list entries, ensuring reporting continuity after migration.

Sage 300cloud tax agencies and tax zones are mapped to Acumatica Tax Agency and Tax Zone entities, and associated tax rates and tax-category assignments are transferred to the corresponding Acumatica Tax settings. Any GST/HST or VAT registration numbers recorded on the entity are preserved on the applicable Tax Agency or Tax Zone record in Acumatica, maintaining compliance information for each legal entity.