Migrate from Sage 200cloud to Acumatica

Sage nominal codes map directly to Acumatica GL accounts. The numeric segment of each Sage code becomes the AccountCD, while the plain‑language name populates the Description field. Any embedded department, cost‑centre, or project suffixes are parsed out and routed to the appropriate subaccount segment in Acumatica. FlitStack generates an account‑mapping specification that lists each source code, its target AccountCD, and the subaccount segment values to be created before import.

Sage 200cloud dimensions (Department, Cost Centre, Project) are flat text values attached to nominal postings. These decompose into Acumatica's multi-segment subaccount structure where each Sage dimension maps to a dedicated segment (e.g. Segment 1 = Department, Segment 2 = Project).

Direct map. Sage customer fields (Account Ref, Name, Address, Credit Limit, Payment Terms, Tax ID) map to the corresponding Acumatica Customer fields. FlitStack extracts customer data via the Sage 200 API or CSV export and loads records into Acumatica using Import Scenarios or the REST API. For multi‑currency customers, Acumatica’s customer‑specific currency settings must be configured before import to ensure correct exchange‑rate handling and payment terms.

Direct map. Sage supplier records map to Acumatica Vendor entities. FlitStack pulls supplier data (Account Ref, Name, Address, Payment Terms, Tax ID, Approved status) via the Sage 200 API or CSV export and loads it using Import Scenarios or the REST API. Before import, Acumatica Vendor classes must be created to accommodate price‑list associations, and any approved‑vendor flags should be mirrored using the appropriate class settings to maintain purchasing controls.

Sage stock items (Part No., Description, Unit of Measure, Stock Group, warehouse locations) map to Acumatica Inventory IDs. Items marked as non-stock in Sage map to Acumatica Non-Stock Items. Bom relationship requires Acumatica Bill of Materials configuration before component-level import.

Open Sage SOP orders with status 'Held' or 'In Progress' migrate to Acumatica Sales Orders with the same status. Despatch records become Acumatica Shipment documents. Fully invoiced Sage orders are not migrated; their invoice data lives in the AP/AR modules.

Open Sage POP orders are extracted via the Sage 200 API or CSV report and loaded into Acumatica as Purchase Orders. FlitStack sets them to a Held or Quotation status for review before release. Line items, promised dates, and vendor references are preserved. Goods Received records map to Acumatica Purchase Receipts, while invoiced POP records are skipped; their AP invoice data migrates as vendor transactions in the AP module.

Sage GL journals (date, account, debit/credit, analysis dimensions, tax code) map to Acumatica GL Batch entries. Sage dimension codes become subaccount segments in Acumatica. Tax codes require a tax agency and tax jurisdiction setup in Acumatica before tax posts can be reconciled.

Sage AR invoices and credit notes map to Acumatica AR Invoices and AR Credit Memos. Sage AP invoices map to Acumatica AP Bills and AP Credit Memos. Open items migrate with outstanding amounts and due dates; cleared items migrate as historical records.

Sage cash‑book bank accounts are extracted via the Sage 200 API or CSV export and mapped to Acumatica Cash Account records, preserving the source bank account number and currency. Bank reconciliation data (statement lines, matched transactions) is not transferred; Acumatica’s bank reconciliation workflow runs on imported bank‑statement files after go‑live, and the team reconciles using Acumatica’s matching tools.

Sage 200cloud contact records are extracted via the Sage 200 API or CSV export and mapped to Acumatica Contacts, preserving name, email, phone, and role. Duplicate contacts are identified by email match and resolved before import. Associated activity records (calls, emails) are loaded as Acumatica Activity entities linked to the corresponding Contact, retaining original timestamps and descriptions.

Sage Projects module or Sicon Projects data maps to Acumatica Projects. If Sage uses custom project-tracking fields (budget codes, WBS codes), these require custom fields on the Acumatica Project entity. Sicon-specific fields are preserved as reference notes or custom attributes.

Sicon Manufacturing BOMs require Acumatica Manufacturing (Basic or Advanced) to be licensed and configured before migration. FlitStack preserves BOM data in a reference export; the Acumatica manufacturing setup plan is delivered separately and not included in the data migration scope.

Sage 200cloud user accounts are extracted via the Sage 200 API or CSV export and mapped to Acumatica Employee records, preserving name, email, and role. Owner resolution uses email as the matching key; FlitStack flags any unmatched emails before migration. All owners must be provisioned in Acumatica before transaction owner fields can be confirmed.