ERP migration

Migrate from De Facto ERP to Acumatica

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 logo

De Facto ERP

Source

Acumatica

Destination

Acumatica logo

Compatibility

100%

12 of 12

objects map 1:1 between De Facto ERP and Acumatica.

Complexity

BStandard

Timeline

3–6 months

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

De Facto ERP logo

De Facto ERP

What's pushing teams away

  • Very few verified reviews exist publicly, making independent evaluation difficult and suggesting a small customer base or low market visibility for a product in this category.
  • Pricing is not publicly transparent — all tiers require direct contact with sales, which creates friction for prospects evaluating cost against alternatives like Odoo or NetSuite.
  • Ease of use scores are notably low (1.5/5 on Capterra) compared to competitors, indicating the steep customization capability comes at the cost of usability for some users.
  • Support ratings are also low (1.0/5 on Capterra), suggesting that post-implementation support may not match the strong implementation partnership experience.

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 De Facto ERP objects map to Acumatica

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

maps to

Acumatica

Customer (AR303000)

1:1
Fully supported

De 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

maps to

Acumatica

Vendor (AP303000)

1:1
Fully supported

De 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

maps to

Acumatica

Inventory Item (IN202500)

1:1
Fully supported

De 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

maps to

Acumatica

BOM / Non-Stock Item (IM303000)

1:1
Fully supported

De 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

maps to

Acumatica

Sales Order (SO301000)

1:1
Fully supported

Open 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

maps to

Acumatica

Purchase Order (PO301000)

1:1
Fully supported

De 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

maps to

Acumatica

AR Invoice (SO501000)

1:1
Fully supported

De 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

maps to

Acumatica

Payment (AR302000)

1:1
Fully supported

De 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

maps to

Acumatica

Journal Transaction (GL301000)

1:1
Fully supported

De 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

maps to

Acumatica

Custom Field (Usr-prefixed)

1:1
Fully supported

Every 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

maps to

Acumatica

File Storage / Note

1:1
Fully supported

De 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

maps to

Acumatica

Contact (CR302000)

1:1
Fully supported

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

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.

De Facto ERP logo

De Facto ERP gotchas

High

No documented public API for programmatic extraction

High

Highly customized deployments resist template migrations

Medium

Pricing is opaque — all tiers require sales contact

Medium

Limited public review volume and low category ratings

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

  • Acumatica Import by Scenario enforces field-level validation before records commit — invalid values halt the entire batch

    De Facto allows free-form text in many fields (addresses, notes, custom properties) while Acumatica's Import by Scenario treats every field as validated input. If a De Facto record contains a postal code in the wrong format, a missing required field like TaxZoneID, or a reference to a non-existent branch, the entire import batch stops and rolls back. We run a pre-validation pass against a sample export before the full migration to surface field-level mismatches. Zip codes with leading zeros, state abbreviations, and date formats are the most common culprits — we build a data-cleansing step into the migration plan that corrects these before any Acumatica import begins.

  • Acumatica custom fields require a customization project with the Usr prefix — they cannot be added inline during import

    De Facto custom fields and user-defined properties are stored within its EDP schema without a prefix convention. Acumatica requires all custom fields to be defined in a customization project using the Usr prefix before any data can be written to them. If De Facto has 30 custom properties across customers, vendors, and inventory items, all 30 must be pre-created in Acumatica's customization project (SM204505) before migration data touches those fields. We deliver a complete custom-field manifest during discovery, but the actual schema creation in Acumatica requires an admin or partner login. This planning step typically adds two to four weeks to the project timeline before data can move.

  • Multi-company De Facto deployments require Acumatica branch or tenant planning before data lands

    De Facto installations with separate legal entities often use distinct company databases or schema-level partitioning to isolate ledgers. Acumatica's branch model can represent these entities within a single tenant, but branch configuration (Company branch settings, inter-company elimination accounts, and tax agency assignments) must be set up before transactional data imports. If De Facto uses separate databases per entity, we need to establish Acumatica branches first and map each De Facto database to its corresponding branch ID during the migration plan. Post-migration, inter-company transactions will not reconcile correctly if branch setup is incomplete when invoices are imported.

  • De Facto landed-cost allocations (freight, duty, insurance) map to Acumatica Carrier subentities, not a single field

    De Facto inventory items frequently carry landed-cost percentages for freight, import duty, and insurance that are stored as attributes on the item record. Acumatica does not store landed cost as a single percentage on the inventory item — instead, it uses Carrier-landed cost codes attached to shipment receipts. Migrating De Facto's landed-cost fields requires creating Acumatica Carrier records (PO503010) and mapping each De Facto landed-cost percentage to the appropriate Carrier-landed cost rule. Items that rely on De Facto's landed-cost calculation for margin reporting will need a recalibrated cost layer in Acumatica after migration.

  • De Facto document templates and SSRS reports do not export in a format Acumatica can consume

    De Facto ERP generates PDF invoices, statements, and purchase order documents using Microsoft SSRS templates with TSQL data sources. Acumatica uses its own report designer and generic inquiries to build documents — there is no automated path to convert SSRS templates into Acumatica report definitions. We export De Facto report layouts as PDF reference copies so your Acumatica admin can recreate them using Acumatica's report designer or a BI tool. This is a manual rebuild step estimated at two to five days per complex report, and it is excluded from the data migration scope.

Migration approach

Six steps for a successful De Facto ERP to Acumatica data migration

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

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

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

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

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

Context on both ends of the pair

De Facto ERP logo

De Facto ERP

Source

Strengths

  • Highly customizable ERP that adapts to company-specific processes rather than forcing standard templates
  • Proprietary EDP (Enterprise Data Platform) architecture designed for flexible, scalable deployment
  • Strong long-term customer partnerships with some clients using the system for decades
  • Handles complex supply chain scenarios including landed costs, landed-cost tracking for importers, and warranty stock management
  • Active implementation support that helps customers migrate existing processes while identifying improvements

Weaknesses

  • Very few publicly verified reviews, making independent evaluation challenging
  • All pricing requires direct sales contact, creating evaluation friction
  • Low ease-of-use scores compared to category alternatives
  • Support quality ratings are inconsistent based on available reviews
  • No documented public API for programmatic data extraction or integration
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 De Facto ERP 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

    De Facto ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your De Facto ERP 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 De Facto ERP to Acumatica data migrations

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

Can't find your answer?

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 consultation

Most De Facto ERP to Acumatica migrations complete in 3–6 months of elapsed time for standard-module setups with fewer than 50,000 records. The longest phase is typically the Acumatica schema preparation — creating branches, tax zones, and custom fields — which requires admin access and typically runs 2–4 weeks. Multi-entity De Facto configurations or manufacturing BOM migrations push timelines to 6–9 months because each legal entity requires its own Acumatica branch with inter-company elimination accounts configured.

Adjacent paths

Related migrations to explore

Ready when you are

Move from De Facto ERP.
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