ERP migration
Field-level mapping, validation, and rollback between FACT ERP.NG and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
FACT ERP.NG
Source
Acumatica
Destination
Compatibility
11 of 12
objects map 1:1 between FACT ERP.NG and Acumatica.
Complexity
BStandard
Timeline
3–6 weeks
Overview
FACT ERP.NG and Acumatica both serve SMEs but their data architectures diverge significantly. FACT ERP.NG stores customers, vendors, items, and transactions in a flat relational model optimised for fast single-company processing — Acumatica layers all of these into a branch-and-sub-ledger model that separates nominal posting from transactional detail and enforces currency-level controls on every document. The migration carries FACT's core transactional recordset (AR/AP ledgers, inventory movements, sales orders, purchase orders) into Acumatica's batch-posting model. The harder problems are mapping FACT's account codes to Acumatica's chart-of-accounts structure with financial dimension segments, resolving FACT's flat address book against Acumatica's Location-per-address hierarchy, and deciding whether FACT's CRM contacts route to Acumatica's Customer Contacts or a standalone Contact directory. FACT's 600+ annual configuration updates and 29-day go-live history do not carry across — workflow routing, approval sequences, and field-level business rules built inside FACT's configuration layer need to be rebuilt as Acumatica screen-level configuration, workflow maps, or customisation-project code.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a FACT ERP.NG object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
FACT ERP.NG
Customer
Acumatica
Customer (AR303000) + Location sub-record
1:1FACT customers map to Acumatica Business Accounts (CustomerClass keyed on AR202010). The primary contact on the FACT customer becomes the primary Location's contact. FACT address fields are split into Location addresses on the Locations sub-grid. Multi-contact accounts require additional Location rows.
FACT ERP.NG
Vendor
Acumatica
Vendor (AP303000) + Location sub-record
1:1FACT vendors map to Acumatica Vendors (VendorClass on AP202010). The vendor's primary address and contact live on the default Location. AP terms on the vendor record (Net 30, Net 60) map to Terms objects (AP204000). FACT vendor 1099 flag migrates to the Acumatica VenPmtMethod field.
FACT ERP.NG
Product / Item
Acumatica
Stock Item / Non-Stock Item (IN202500)
1:1FACT items with on-hand stock become Acumatica Stock Items (ItemType = GI); service-only items become Non-Stock Items (ItemType = NS). The FACT stock-valuation method (Average/FIFO) maps to the ItemValMethod dropdown on IN202500. FACT item class grouping maps to Acumatica's Item Class (IN201500) for shared posting settings.
FACT ERP.NG
Sales Order
Acumatica
Sales Order (SO301000) + SOLine (SOLine) + SOShipLine
1:1FACT sales orders map 1:1 to Acumatica Sales Orders. Order number maps to OrderNbr; order date maps to OrderDate; customer reference maps to CustomerOrderNbr. FACT line-level discount % maps to the Discount安稳t field on SOLine. Pending-ship lines create open SOShipLine records in Acumatica.
FACT ERP.NG
Purchase Order
Acumatica
Purchase Order (PO301000) + POLine
1:1FACT purchase orders map to Acumatica Purchase Orders. The vendor on the FACT PO maps to the VendorID on PO301000. Line-level item, quantity, and cost map to POLine inventory ID, OrderQty, and CuryUnitCost respectively. Open status FACT POs remain in the Open state in Acumatica; completed POs are set to Completed.
FACT ERP.NG
AR Invoice
Acumatica
AR Invoice (AR301000) + ARTran
1:1FACT AR invoices map to Acumatica AR Invoices. The document number maps to RefNbr; invoice date maps to DocDate; due date maps to DueDate. Line-level tax amounts from FACT map to Tax Category on ARTran with Acumatica tax setup (TX205000) applied post-migration. Fact batch numbers map to the BatchNbr field linked to the GL batch.
FACT ERP.NG
AP Invoice
Acumatica
AP Invoice (AP301000) + APTran
1:1FACT AP invoices map to Acumatica AP Invoices. Vendor reference number maps to VendorRefNbr. Tax amounts from the FACT invoice map to Tax Category on APTran. If the FACT AP invoice is linked to a PO, the Acumatica AP invoice is created as a Prepayment or Regular document linked to the POLine via the POLinkRefNbr.
FACT ERP.NG
GL Account
Acumatica
GL Account (GL202500) + Subaccount (CR205010)
1:1FACT's flat account codes map to Acumatica's segmented COA (e.g., 100-1100-CASH). FACT sub-account codes become Acumatica Subaccounts keyed by SubaccountCD. Acumatica's segment count and segment masks are defined in the Chart of Accounts screen (GL101000) before any accounts are created. Account types (Asset, Liability, Income, Expense) map to the Type field on GL202500.
FACT ERP.NG
FACT User / Owner
Acumatica
Acumatica Employee (EP301000) + User (SM201010)
1:1FACT user IDs are matched by email to Acumatica Employees. The Employee record links to the Acumatica User account via the internal EmployeeID. FACT owner assignments on transactions (Created By, Approved By) map to the EmployeeID on the Acumatica document header. Users without a matching Acumatica account are flagged for admin creation before migration.
FACT ERP.NG
FACT Warehouse / Location
Acumatica
Warehouse (WH203000) + Location (WH204000)
1:1FACT warehouses with bin-level tracking map to Acumatica Warehouses (WH203000). FACT bin codes map to Location records under the Warehouse (WH204000). Acumatica requires the warehouse to exist before inventory transactions referencing it can be posted. FIFO/batch-tracked FACT warehouses require the Lot/Serial Class on the warehouse to be set correctly on WH203000.
FACT ERP.NG
FACT CRM Contact
Acumatica
Contact (CR302000) + Business Account Contact (CR3020PL)
1:manyFACT contacts that are direct customers (B2C) route to standalone Acumatica Contacts (CR302000) linked to the Account. FACT contacts that are employees of a vendor company route to Contact records linked to the Vendor Business Account. FACT contact roles (Decision Maker, Influencer) are stored as a custom pick-list on the contact relationship (CR3020PL) rather than a separate association label.
FACT ERP.NG
FACT Tax Code
Acumatica
Tax Zone (TX205000) + Tax (TX202000)
1:1FACT tax codes (e.g., S3-GST-7) map to Acumatica Tax records. The FACT tax rate percentage and tax type (inclusive/exclusive) are used to configure the Acumatica Tax record's Rate and ExpenseAccrual account. Value-mapping is required because FACT allows free-text tax codes whereas Acumatica requires Tax IDs registered in TX202000.
| FACT ERP.NG | Acumatica | Compatibility | |
|---|---|---|---|
| Customer | Customer (AR303000) + Location sub-record1:1 | Fully supported | |
| Vendor | Vendor (AP303000) + Location sub-record1:1 | Fully supported | |
| Product / Item | Stock Item / Non-Stock Item (IN202500)1:1 | Fully supported | |
| Sales Order | Sales Order (SO301000) + SOLine (SOLine) + SOShipLine1:1 | Fully supported | |
| Purchase Order | Purchase Order (PO301000) + POLine1:1 | Fully supported | |
| AR Invoice | AR Invoice (AR301000) + ARTran1:1 | Fully supported | |
| AP Invoice | AP Invoice (AP301000) + APTran1:1 | Fully supported | |
| GL Account | GL Account (GL202500) + Subaccount (CR205010)1:1 | Fully supported | |
| FACT User / Owner | Acumatica Employee (EP301000) + User (SM201010)1:1 | Fully supported | |
| FACT Warehouse / Location | Warehouse (WH203000) + Location (WH204000)1:1 | Fully supported | |
| FACT CRM Contact | Contact (CR302000) + Business Account Contact (CR3020PL)1:many | Fully supported | |
| FACT Tax Code | Tax Zone (TX205000) + Tax (TX202000)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
FACT ERP.NG gotchas
Configuration parameters must be mapped as first-class migration objects
Payroll journal entries create a mandatory sequencing dependency with the GL
Slow report rendering can extend migration validation cycles
No publicly documented API for direct programmatic extraction
Dashboard configurations are not exportable data objects
Acumatica gotchas
API user licenses cap concurrent sessions and request throughput
Multi-tenant filtering requires CompanyID awareness
Custom fields require separate discovery before field mapping
Notes and attachments use a separate linked table structure
Implementation timelines frequently run 3–9 months end-to-end
Pair-specific challenges
Migration approach
Extract FACT data via API and direct query
FlitStack AI connects to the FACT ERP.NG instance using the published REST API endpoints for master data (customers, vendors, items) and transactional documents (sales orders, purchase orders, AR/AP invoices). Where the API does not cover historical records or custom fields, we run read-only SQL queries against the FACT database with customer-supplied credentials. All extracts are written to an intermediate schema and checksummed for completeness before transformation begins.
Stand up Acumatica chart of accounts and numbering sequences
Before any transactional data is written, the migration plan builds the Acumatica COA structure (GL202500) to match FACT's account code hierarchy, adds subaccounts for any FACT cost-centre codes, and configures Numbering Sequences (SM204000) for each document type (AR Invoice, AP Invoice, SO, PO). This step also configures the base currency in SM200505, enables the required modules (AR, AP, SO, PO, IN, GL), and sets the posting profiles that determine where migrated documents land in the general ledger.
Migrate master data first: accounts, locations, items, vendors, warehouses
Master data migration runs in dependency order: GL accounts and subaccounts first (required by all other records), then Warehouses (required by inventory items), then Inventory Items (required by purchase and sales orders), then Vendors (required by AP and PO), then Customers (required by AR and SO). Each record type is bulk-loaded using Acumatica's import infrastructure. Location records for each Customer and Vendor are created in the same batch. FACT document references are preserved in a custom SourceDocNbr field on the Acumatica record for cross-system reconciliation.
Migrate transactional records: open and historical orders, AR/AP documents
With master data in place, FlitStack AI loads FACT open sales orders and purchase orders into Acumatica SO and PO screens, preserving line items, quantities, and pricing. AR and AP documents from FACT are loaded as open documents in Acumatica AR301000 and AP301000, each linked to a GL batch. Historical paid invoices and closed orders are migrated as read-only history records (status = Closed) to preserve the audit trail without creating open items. FACT batch-reference numbers are stored in the BatchNbr field for GL audit traceability.
Run sample migration and field-level diff before full commit
A representative slice — typically 100–300 records spanning customers, vendors, items, and open orders — is migrated into a test Acumatica company. FlitStack AI generates a field-level diff comparing source FACT values against the Acumatica target values, flagging any value-mapping gaps, currency mismatches, or truncated fields. The diff is reviewed with the customer before the full migration run is scheduled. Key checkpoints include: Location hierarchy coverage for multi-address FACT customers, GL account assignment on AR/AP documents, and currency alignment.
Delta-cutover with in-flight capture and rollback option
The full migration commits to the production Acumatica tenant. During the cutover window (typically 24–48 hours), a delta capture monitors the FACT source for any new or modified records created after the initial extract timestamp. Those delta records are appended to the migration set. An audit log records every record inserted, updated, or skipped. FlitStack AI provides a one-click rollback that removes all migrated records from Acumatica and re-runs the extract from FACT if reconciliation fails, allowing the team to restart the cutover cleanly without data duplication.
Platform deep dives
FACT ERP.NG
Source
Strengths
Weaknesses
Acumatica
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across FACT ERP.NG and Acumatica.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
FACT ERP.NG: Not publicly documented.
Data volume sensitivity
FACT ERP.NG doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during FACT ERP.NG to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your FACT ERP.NG to Acumatica migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave FACT ERP.NG
Other ways to arrive at Acumatica
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.