ERP migration

Migrate from FACT ERP.NG to Acumatica

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 logo

FACT ERP.NG

Source

Acumatica

Destination

Acumatica logo

Compatibility

92%

11 of 12

objects map 1:1 between FACT ERP.NG and Acumatica.

Complexity

BStandard

Timeline

3–6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

FACT ERP.NG logo

FACT ERP.NG

What's pushing teams away

  • Slow report rendering and processing delays—users report waiting extended periods for what should be quick queries, especially on larger datasets with full period ranges.
  • Limited depth in certain functional areas—some users supplement FACT ERP.NG with separate software for tasks like advanced HR analytics or niche manufacturing scheduling that the built-in modules do not fully cover.
  • Learning curve for new users despite ease-of-use claims—while the interface is familiar to power users, employees unfamiliar with integrated ERP workflows require structured training before becoming productive.
  • Customisation constraints frustrate niche industry requirements—the Configuration Only model means businesses with highly specific workflows sometimes cannot adapt the system without workaround processes.

Choosing

Acumatica logo

Acumatica

What's pulling them in

  • Unlimited user licensing lets companies add staff without per-seat billing shocks, making Acumatica cost-predictable at scale.
  • Flexibility and scalability earn consistent praise — users value a platform that adapts to vertical workflows without forcing a redesign.
  • Real-time visibility across financials, inventory, and projects gives mid-market businesses a consolidated operational view previously available only in enterprise-tier ERPs.
  • Cloud-native architecture with automatic updates removes infrastructure management burden from in-house IT teams.
  • Modular licensing lets companies start with one or two suites (Financials, Distribution) and expand into Manufacturing or CRM incrementally.

Object mapping

How FACT ERP.NG objects map to Acumatica

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

maps to

Acumatica

Customer (AR303000) + Location sub-record

1:1
Fully supported

FACT 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

maps to

Acumatica

Vendor (AP303000) + Location sub-record

1:1
Fully supported

FACT 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

maps to

Acumatica

Stock Item / Non-Stock Item (IN202500)

1:1
Fully supported

FACT 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

maps to

Acumatica

Sales Order (SO301000) + SOLine (SOLine) + SOShipLine

1:1
Fully supported

FACT 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

maps to

Acumatica

Purchase Order (PO301000) + POLine

1:1
Fully supported

FACT 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

maps to

Acumatica

AR Invoice (AR301000) + ARTran

1:1
Fully supported

FACT 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

maps to

Acumatica

AP Invoice (AP301000) + APTran

1:1
Fully supported

FACT 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

maps to

Acumatica

GL Account (GL202500) + Subaccount (CR205010)

1:1
Fully supported

FACT'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

maps to

Acumatica

Acumatica Employee (EP301000) + User (SM201010)

1:1
Fully supported

FACT 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

maps to

Acumatica

Warehouse (WH203000) + Location (WH204000)

1:1
Fully supported

FACT 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

maps to

Acumatica

Contact (CR302000) + Business Account Contact (CR3020PL)

1:many
Fully supported

FACT 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

maps to

Acumatica

Tax Zone (TX205000) + Tax (TX202000)

1:1
Fully supported

FACT 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.

Gotchas + challenges

What specifically takes care here

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 logo

FACT ERP.NG gotchas

High

Configuration parameters must be mapped as first-class migration objects

High

Payroll journal entries create a mandatory sequencing dependency with the GL

Medium

Slow report rendering can extend migration validation cycles

Medium

No publicly documented API for direct programmatic extraction

Low

Dashboard configurations are not exportable data objects

Acumatica logo

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

  • FACT's flat customer address vs Acumatica's Location hierarchy

    FACT stores address fields directly on the customer record. Acumatica requires addresses to live on Location sub-records under the Business Account. Migration must split each FACT address into a default Location record with the same address values, then handle any secondary FACT addresses (billing vs shipping) as additional Location rows. If FACT uses a single address for both billing and shipping, the default Location is created with both address and shipping overrides unchecked, which Acumatica resolves at order time from the Location's settings. Failure to create the Location hierarchy first means Acumatica rejects the customer insert with a validation error at SOOrder creation.

  • Acumatica's batch-posting model requires GL batch creation before transactional inserts

    Acumatica AR and AP documents do not post directly to ledgers — they create GL batches via the posting process. Migration scripts must account for this: each AR/AP document in Acumatica has a BatchNbr field that points to a GL batch in GL300000. FlitStack AI creates the GL batch header first (BatchNbr, Module, Date, LedgerID), then inserts the AR/AP document linked to that batch. FACT documents do not have an equivalent batch concept — their GL entries are implied by the account assignments. The migration plan must define the posting class on the AR/AP document screen (AR202010, AP202010) and the default GL account in the posting profile before documents land, otherwise all migrated documents post to the suspense account configured in GL004000.

  • Multi-currency setup must be completed before any transactional records import

    Acumatica enforces CuryID on every transaction line when multi-currency is enabled at the tenant level. If FACT uses a single currency (e.g., SGD) and Acumatica is configured with SGD as the base currency, the CuryID on migrated records will be SGD and no exchange-rate lookup occurs. If FACT uses multiple currencies and Acumatica's base is set differently, every document line must carry a CuryRate from an exchange rate provider configured in CM202000 (Currency Rates). The base currency on the tenant is set in the Management Information tab of SM200505 and cannot be changed after the first financial transaction posts. Migrating multi-currency FACT records into a single-currency Acumatica tenant without currency alignment first produces zero-amount line errors at document-release time.

  • FACT document-number sequences may conflict with Acumatica's Numbering Sequence validation

    FACT allows free-form document numbers including alphabetic prefixes and embedded separators. Acumatica's Numbering Sequence (SM204000) validates the format against a defined pattern (e.g., AR-INV-####). Records whose RefNbr does not match the active sequence are rejected at save. FlitStack AI inspects all FACT document numbers before migration, maps them to Acumatica Numbering Sequences with matching patterns, and flags any FACT numbers that cannot conform. For unmatched FACT numbers, we configure a separate 'Imported' numbering sequence with a wildcard mask (e.g., IMP-####-######) to accept the raw FACT value and preserve traceability via the Source field on GLTrans.

  • FACT's configuration-only custom fields require re-implementation as Acumatica DAC extensions

    FACT's configuration layer adds fields to screens without modifying the underlying database schema in a way that is directly portable. Acumatica custom fields require a Customisation Project (Customization Project Editor in the ISV Workspace) with DAC extension classes declaring the field with PXString, PXInt, or PXDecimal attributes. The DAC extension must be published to the Acumatica tenant before data can be inserted into the custom field. FACT custom fields used in business rules (e.g., regional cost-centre codes, branch-level approval flags) must be documented as a separate re-implementation workstream in the migration plan.

Migration approach

Six steps for a successful FACT ERP.NG to Acumatica data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

FACT ERP.NG logo

FACT ERP.NG

Source

Strengths

  • Configuration-only deployment with 29-day go-live and no coding required
  • 600+ updates per year included in annual subscription with zero downtime
  • Integrated e-invoicing for Malaysian (LHDN) and Singapore (InvoiceNow) compliance
  • Real-time data sharing across financials, CRM, inventory, manufacturing, and payroll
  • Fast CXO Control Tower dashboard reporting across the full data model

Weaknesses

  • Processing speed degrades on large datasets or full period-range reports
  • Configuration-only model limits adaptation for niche industry workflows
  • Limited depth in certain modules may require third-party supplementation
  • Dashboard exports and API capabilities are not publicly documented for migration tooling
  • No public pricing—quotes are custom per company size and turnover
Acumatica logo

Acumatica

Destination

Strengths

  • Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
  • Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
  • Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
  • Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
  • Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

  • Steep learning curve and complex initial setup create significant onboarding friction.
  • Report Designer is widely cited as unintuitive and difficult to use for non-developers.
  • Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
  • Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
  • API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across FACT ERP.NG and Acumatica.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    FACT ERP.NG: Not publicly documented.

  • Data volume sensitivity

    B

    FACT ERP.NG doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your FACT ERP.NG to Acumatica migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about FACT ERP.NG to Acumatica data migrations

Answers to the questions buyers ask most during FACT ERP.NG to Acumatica migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

FACT ERP.NG to Acumatica migrations typically complete in 3–6 weeks of active migration time for setups under 10,000 transactional records. Larger volumes exceeding 50,000 records, multi-company configurations, or FACT setups using multiple currencies and landed-cost tracking extend the timeline to 8–12 weeks. The longest single step is the Acumatica chart-of-accounts and numbering-sequence configuration before data is imported, which can take 1–2 weeks depending on the complexity of the FACT account structure.

Adjacent paths

Related migrations to explore

Ready when you are

Move from FACT ERP.NG.
Land in Acumatica, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day