Migrate from Sage 100cloud to Acumatica

Sage 100 stores the natural account number in GL_Account_Master; Acumatica receives the natural account portion and maps it to the first segment of the AccountCode. The subaccount portion is read from GL_Subaccount_Master and concatenated using the Acumatica segment separator (typically a dash or period) in the second and subsequent segments.

Sage 100 subaccounts encode department, cost center, division, project, or any other analytical dimension. Acumatica maps each Sage 100 subaccount type to a named segment in its chart of accounts configuration. A client with two subaccount dimensions (e.g., department and project) will map to a two-segment Acumatica account structure. The migration plan specifies which subaccount values map to which segment position before any GL data is loaded.

Sage 100 customers map to Acumatica Customers with direct field correspondence on customer number, name, credit limit, payment terms, and tax group. Customer addresses in Sage 100's separate address table map to Acumatica's Address selectable view on the Customer screen. Primary contact names and email addresses from the Sage 100 contact subfile map to the Customer's default Contact record.

Sage 100 vendors map to Acumatica Vendors with direct correspondence on vendor number, name, payment terms, and 1099 flag. Sage 100's separate vendor address table maps to Acumatica's Address selectable view. Remit-to addresses in Sage 100 map to the Vendor's Remit-To address override.

Sage 100 inventory items map to Acumatica StockItems (for physical goods) or Non-Stock Items (for services and non-inventoried parts). Unit of measure conversions from Sage 100's U/M table map to Acumatica's UOM definition screen. The item's costing method (FIFO, Average, Standard) is read from the Sage 100 Inventory Master and applied as the Acumatica Cost Method on the Stock Item — this is a critical mapping point because Acumatica enforces one cost method per company, and open-layer alignment must be verified before go-live.

Sage 100 warehouses map to Acumatica Warehouses with location codes and addresses preserved. Warehouse-specific bin locations in Sage 100 map to Acumatica bin definitions within each Warehouse. If Sage 100 uses lot or serial number tracking, those settings are read from the Inventory Master and replicated in Acumatica's lot/serial number configuration.

Sage 100 open AR invoices (invoice number, customer, invoice date, due date, terms, amount, GL distribution) map to Acumatica AR Invoices. Line items from Sage 100's invoice detail table map to Acumatica's detail lines with inventory ID, warehouse, quantity, and unit price. Prepayments and credit memos are migrated as separate document types (PM Adjustment, Credit Memo) to preserve open-balance continuity.

Sage 100 open AP invoices map to Acumatica AP Bills. Line items are loaded with vendor part number, description, and GL account distribution. Sage 100 check register history maps to Acumatica Payments Applied to AP Bills for reconciliation continuity. Held or disputed invoices are migrated with their status flags so AP staff can continue review workflows.

Sage 100 journal entries map to Acumatica General Ledger Journal transactions. Each line references the Acumatica AccountCode (with concatenated subaccount segments) and carries the source module identifier so the entry is visible in the originating module report. Recurring journal entries from Sage 100 are exported as templates and handed off to the Acumatica administrator for rebuild in the Recurring Schedules screen.

Sage 100 bill-of-materials records (parent item, component items, quantities, operation steps, work center) map to Acumatica's Bill of Materials screen. Engineering BOMs and manufacturing BOMs are distinguished in Sage 100 and carry that distinction into Acumatica's BOM type field. If Sage 100 uses phantom BOMs or co-products, those structures are documented and a rebuild specification is delivered alongside the migration data.

Sage 100 open sales orders map to Acumatica Sales Orders. Header-level fields (order number, customer, order date, warehouse, shipping terms) and line-level fields (inventory ID, quantity, unit price, discount, line total) are migrated. Closed and fulfilled orders are migrated as historical records for reporting continuity rather than as active documents.

Sage 100 custom VB scripts and third-party add-on logic (e.g., AcuRental, AcuCommissions, AcuContainer mentioned in reseller materials) do not have a migration path to Acumatica. FlitStack AI catalogues every active custom library, add-on, and ISV module in a companion rebuild specification document and delivers it to your Acumatica implementation team for recreation using Acumatica's Customization Project framework.

Sage 100 user accounts and role-based security permissions (which screens and modules each user can access) have no direct equivalent in Acumatica. FlitStack AI exports the Sage 100 user list with role assignments as a reference CSV and hands it to your Acumatica administrator to configure in Acumatica's Access Rights screen using the same role-naming conventions for familiarity.