ERP migration
Field-level mapping, validation, and rollback between De Facto ERP and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
De Facto ERP
Source
Acumatica
Destination
Compatibility
12 of 12
objects map 1:1 between De Facto ERP and Acumatica.
Complexity
BStandard
Timeline
3–6 months
Overview
De Facto ERP organizes data around its Enterprise Data Platform (EDP) with modules for product supply chain, financials, CRM, and document management. Acumatica uses a component-based application model where Customers, Vendors, Inventory, Sales Orders, Purchase Orders, and Financial Ledgers exist as discrete entities with their own screens and APIs. The migration carries De Facto's customer and supplier records, inventory items with landed-cost data, open and closed orders, and any custom fields into the corresponding Acumatica entities. Custom fields in De Facto require mapping to Acumatica's Usr-prefixed custom field convention, and multi-company De Facto setups map to Acumatica branches or separate tenant configurations. We run the migration against Acumatica's Import by Scenario API, which enforces field-level validation before records commit. Workflow configurations, document templates, and custom report definitions do not migrate — we export them as reference documentation for your Acumatica admin to rebuild. The migration also preserves De Facto's audit trail timestamps, user ownership, and attachments, ensuring continuity of historical records. Post‑migration, your team can leverage Acumatica's role‑based security to reassign permissions that mirror De Facto's access controls. Because Acumatica's API supports OData, future integrations with third‑party e‑commerce or EDI platforms become straightforward.
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 De Facto ERP 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.
De Facto ERP
Customer
Acumatica
Customer (AR303000)
1:1De Facto customer records map directly to Acumatica's Customers screen. Primary contact details, billing address, and terms move as-is. De Facto's credit-limit field maps to Acumatica's CreditLimit attribute. Customers without a primary contact link surface as orphaned records and require a default contact to be assigned before validation passes.
De Facto ERP
Supplier / Vendor
Acumatica
Vendor (AP303000)
1:1De Facto supplier records migrate to Acumatica Vendors. Payment terms, remittance address, and tax ID map field-for-field. De Facto's landed-cost allocation rules require translation into Acumatica's Carrier and LandedCost subentities — this is a custom mapping step that we document in the vendor setup plan before import.
De Facto ERP
Inventory Item
Acumatica
Inventory Item (IN202500)
1:1De Facto inventory items carry class codes, stocking UOMs, and landed-cost components. Acumatica uses Stock Items and Non-Stock Items with separate attribute schemas. We split De Facto items by type: stocked items map to Stock Items with the base UOM preserved; non-stocked items (Dropship, special-order) map to Non-Stock Items. Landed-cost freight and duty percentages migrate as Carrier-landed cost codes.
De Facto ERP
Bill of Materials
Acumatica
BOM / Non-Stock Item (IM303000)
1:1De Facto BOM records with component ingredients and quantities map to Acumatica's BOMs (Bill of Materials) screen. Where De Facto supports formula-based BOMs for process manufacturing, Acumatica uses a separate Process Manufacturing extension — if your De Facto BOM uses formulas, we flag this for a dedicated Acumatica manufacturing consultant before migration.
De Facto ERP
Sales Order
Acumatica
Sales Order (SO301000)
1:1Open De Facto sales orders migrate as SO301000 records with line items, scheduled shipments, and owner assignment. Order statuses map via value mapping: De Facto's 'Despatched' maps to Acumatica's 'Completed' and 'Invoiced' state. Historical closed orders migrate as read-only records or are archived based on your retention preference.
De Facto ERP
Purchase Order
Acumatica
Purchase Order (PO301000)
1:1De Facto purchase orders map to Acumatica's PO301000. Line items, vendor references, and expected-receipt dates transfer directly. If De Facto uses multi-line purchase orders with fractional quantities for landed-cost allocation, we flatten those into separate freight lines in Acumatica's receipt-entry screen.
De Facto ERP
Invoice / AR Invoice
Acumatica
AR Invoice (SO501000)
1:1De Facto invoices map to Acumatica's AR Invoice screen. Tax jurisdictions, payment terms, and invoice descriptions preserve their original values. Prepayments and credit memos from De Facto migrate as separate document types (Prepayment and Credit Memo) to preserve their financial standing.
De Facto ERP
Payment / AR Payment
Acumatica
Payment (AR302000)
1:1De Facto cash receipts and payments apply to invoices via payment matching. We preserve the payment amount, date, and reference number, and re-run payment-application matching in Acumatica after migration using invoice document numbers as the key. We also validate that the payment currency matches the invoice currency and that exchange rates are applied correctly.
De Facto ERP
General Ledger Entry
Acumatica
Journal Transaction (GL301000)
1:1De Facto ledger entries map to Acumatica GL journal transactions with account code, debit/credit amount, and description. If De Facto uses multi-segment account codes (Cost Centre, Department, Region), we split those segments into Acumatica's subaccount dimensions using a mapping table built during discovery.
De Facto ERP
Custom Field / User-Defined Property
Acumatica
Custom Field (Usr-prefixed)
1:1Every De Facto custom field requires an Acumatica custom field to be pre-created with the Usr prefix in a customization project before migration data can write to it. We deliver a custom-field manifest listing the field name, data type, and pick-list values so your Acumatica developer or partner creates the schema before data import runs.
De Facto ERP
Document Attachment
Acumatica
File Storage / Note
1:1De Facto attachments (PDFs, images, OCR-processed invoices) migrate to Acumatica's File Storage screen and are linked to the parent record by reference ID. Large attachments exceeding 25MB are flagged for manual review since Acumatica applies file-size limits per upload. We also compress oversized files before upload or store them in an external repository linked via URL.
De Facto ERP
Contact Person
Acumatica
Contact (CR302000)
1:1De Facto contact persons linked to customers or vendors map to Acumatica Contacts. Email, phone, job title, and the IsPrimaryContact flag transfer directly. Contacts without a parent customer are flagged and assigned to a default customer or vendor account before validation.
| De Facto ERP | Acumatica | Compatibility | |
|---|---|---|---|
| Customer | Customer (AR303000)1:1 | Fully supported | |
| Supplier / Vendor | Vendor (AP303000)1:1 | Fully supported | |
| Inventory Item | Inventory Item (IN202500)1:1 | Fully supported | |
| Bill of Materials | BOM / Non-Stock Item (IM303000)1:1 | Fully supported | |
| Sales Order | Sales Order (SO301000)1:1 | Fully supported | |
| Purchase Order | Purchase Order (PO301000)1:1 | Fully supported | |
| Invoice / AR Invoice | AR Invoice (SO501000)1:1 | Fully supported | |
| Payment / AR Payment | Payment (AR302000)1:1 | Fully supported | |
| General Ledger Entry | Journal Transaction (GL301000)1:1 | Fully supported | |
| Custom Field / User-Defined Property | Custom Field (Usr-prefixed)1:1 | Fully supported | |
| Document Attachment | File Storage / Note1:1 | Fully supported | |
| Contact Person | Contact (CR302000)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.
De Facto ERP gotchas
No documented public API for programmatic extraction
Highly customized deployments resist template migrations
Pricing is opaque — all tiers require sales contact
Limited public review volume and low category ratings
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
Discover De Facto schema and Acumatica configuration
FlitStack AI inventories all De Facto entities (customers, vendors, inventory, orders, invoices, GL entries) and any custom fields. We simultaneously map those to the target Acumatica tenant's branch structure, tax zones, and chart of accounts. For multi-company De Facto setups, we identify the entity-to-branch mapping. We deliver a custom-field manifest for your Acumatica admin to create via the customization project (SM204505) before data import begins.
Cleanse and normalize data before Acumatica import
De Facto exports frequently contain formatting inconsistencies — mixed-case addresses, date formats outside ISO 8601, and non-numeric characters in postal codes. We run a data-cleansing pass that corrects field formats, removes duplicate records, and resolves orphaned parent-child relationships (contacts without a customer, invoice lines without a header). The cleansed export is validated against Acumatica's schema requirements before any import batch is built.
Load master data and custom fields into Acumatica
We begin with customer, vendor, and inventory master data using Acumatica's Import by Scenario screens. Custom fields (Usr-prefixed) are populated after the base records are committed. The import runs in batches of 500–2,000 records with field-level validation on each commit. Validation errors are logged with row numbers and field names so corrections can be applied without restarting the entire batch.
Migrate transactional records with referential integrity
Open sales orders, purchase orders, AR invoices, and AP invoices are loaded with their line items. We preserve the original document date, due date, and owner (salesperson) by mapping them to Acumatica's corresponding fields. GL journal entries are imported using the GL Import screen with account-segment mapping from De Facto's multi-dimensional codes to Acumatica's branch and subaccount dimensions. We also ensure that each record's branch assignment aligns with the entity mapping defined during discovery, and we log each import batch to an audit trail for later verification.
Run delta-pickup and reconciliation
After the initial migration, a delta window (24–48 hours) captures any records created or modified in De Facto during cutover. We run a reconciliation report comparing record counts and total amounts by document type between De Facto and Acumatica. If totals match within your specified tolerance (typically 0.01%), the migration is approved for go-live. An audit log captures every import operation, and one-click rollback is available if reconciliation fails.
Platform deep dives
De Facto ERP
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 De Facto ERP 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
De Facto ERP: Not publicly documented.
Data volume sensitivity
De Facto ERP 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 De Facto ERP to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your De Facto ERP 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 De Facto ERP
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.