ERP migration
Field-level mapping, validation, and rollback between WP ERP and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
WP ERP
Source
Acumatica
Destination
Compatibility
13 of 14
objects map 1:1 between WP ERP and Acumatica.
Complexity
BStandard
Timeline
48–72 hours
Overview
WP ERP stores its data in WordPress custom database tables — Contacts and Companies in the CRM module, Employee records in HRM, and GL accounts and invoices in the Accounting module. Acumatica organizes everything around screens and documents: Customers, Vendors, Inventory Items, AR Invoices, AP Payments, and GL Accounts, with multi-entity and branch scoping built into every record. The migration extracts WP ERP data through its WordPress REST API endpoints and direct database access, then loads into Acumatica via its contract-based REST API using the Default/23.200.001 endpoint structure. We map CRM contacts to Acumatica Customers, companies to the Customer.OrganizationName structure, deals to Opportunities, and HRM employees to either Customer or Contact records depending on employment status. GL account codes, department identifiers, and custom field values carry across as Acumatica custom fields. WP ERP workflows and automation rules do not migrate — they must be rebuilt in Acumatica Business Events. We run a sample migration against a representative data slice before the full load, then apply a 24–48 hour delta pickup to capture any in-flight WP ERP records created during cutover.
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 WP 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.
WP ERP
Contact (CRM module)
Acumatica
Customer
1:1WP ERP CRM contacts map to Acumatica Customers with CustomerClass scoping. We populate CustomerName from the contact's display name and email as the Default Email. If the WP ERP contact has an associated company, we link via Customer.SameAsMainContact or create a separate contact record under the customer.
WP ERP
Company (CRM module)
Acumatica
Customer / Organization
1:1WP ERP companies map to the OrganizationName on an Acumatica Customer record. Acumatica treats companies as organizational parents of contacts; we set the CompanyName field on the Customer and link the WP ERP contact as the primary contact. Industry codes from WP ERP become CustomerClass entries.
WP ERP
Deal (CRM module)
Acumatica
Opportunity (CR302000)
1:1WP ERP deal titles, amounts, stages, and close dates load into Acumatica Opportunities linked to the mapped Customer. Deal probability maps to the stage probability on the Opportunity record. If the deal has an owner, we resolve by email against Acumatica Users and set Opportunity.Owner.
WP ERP
Pipeline / Pipeline Stage
Acumatica
Opportunity Stage
1:1WP ERP pipeline stage names (e.g., Won, Lost, Negotiation) map value-by-value to Acumatica Opportunity Stages. We create the Acumatica stage values in the CRM Setup screen before migration if they don't already exist. Stage-entered timestamps are preserved in a custom datetime field.
WP ERP
Employee (HRM module)
Acumatica
Customer / Contact
1:manyWP ERP employees split into two Acumatica destinations based on their HRM employment status. Active employees who need to log into Acumatica become Users and are linked to a Customer record. Former employees or contractors without system access land as Contacts with employment status preserved in a custom field.
WP ERP
Department (HRM module)
Acumatica
Custom field on Contact / Branch
1:1WP ERP departments have no Acumatica native equivalent. We create a Department__c custom field on the Customer/Contact object and populate it with the WP ERP department name. For multi-branch Acumatica setups, departments can alternatively map to Branches, though this requires Acumatica admin configuration.
WP ERP
Pay Grade / Job Title
Acumatica
Custom field on Customer
1:1WP ERP pay grades and job titles from the HRM setup screens migrate as custom pick-list fields on the Customer record (for employee records in Acumatica CRM). We create PayGrade__c and JobTitle__c fields and populate them from the employee's wp_erp_hr_employee record.
WP ERP
Chart of Accounts (Accounting module)
Acumatica
GL Account (GL202000)
1:1WP ERP accounting module account codes and names load directly into Acumatica GL Accounts. We map AccountCode to AccountCD and AccountName to Description. Subaccount segments in Acumatica (configured in CO205000) require setup if WP ERP uses multi-segment account codes. During extraction we read wp_erp_acct_chart_of_accounts and transform any hierarchical structures into flat GL accounts, preserving original account IDs and active status.
WP ERP
Invoice (Accounting module)
Acumatica
AR Invoice (AR301000)
1:1WP ERP invoices become Acumatica AR Invoices. Invoice number maps to ReferenceNbr, total amount to CuryOrigDocAmt, and the invoice date to DocDate. The linked customer is resolved from the WP ERP invoice's customer association. Line items load into ARTran with inventory item or description-only entries.
WP ERP
Vendor / Payee
Acumatica
Vendor (AP303000)
1:1WP ERP accounting vendors map to Acumatica Vendors. VendorName and the primary email or address carry across. If WP ERP stores vendor records in its CRM module (shared contact types), we differentiate vendors from customers using the contact type field and route accordingly.
WP ERP
Note / Activity
Acumatica
Note / Activity (CR306020)
1:1WP ERP CRM notes and activity records (calls, tasks, meetings) migrate to Acumatica Activities linked to the parent Customer or Opportunity. Original timestamps and assigned owners carry across. Activities without a parent record land in a general Activity list for manual re-assignment.
WP ERP
Workflow / Automation
Acumatica
No equivalent — rebuild required
1:1WP ERP Workflow extension rules (triggers on email, contact creation, deal stage change) have no Acumatica native equivalent. We export the rule definitions from wp_erp_workflow as JSON so your Acumatica admin can recreate them as Business Events and Action categories in the CRM preferences.
WP ERP
Custom Field (Custom Field Builder extension)
Acumatica
Custom field (entity.custom)
1:1Custom fields built in WP ERP's Custom Field Builder store their values in wp_erp_custom_fields_meta with serialized PHP data. We deserialize and map each custom field to an Acumatica custom field on the appropriate entity (Contact, Customer, Employee, etc.). Field types are translated: text to string, number to integer/decimal, pick-list to Acumatica combo field.
WP ERP
WooCommerce Order (via WooCommerce CRM integration)
Acumatica
Sales Order (SO301000)
1:1If WP ERP has the WooCommerce integration active and orders are stored, they map to Acumatica Sales Orders. Order number becomes the Acumatica order's CustomerOrderNbr field. Line items map to SOLine with inventory items resolved by SKU. The WooCommerce order total reconciles against the Acumatica order total.
| WP ERP | Acumatica | Compatibility | |
|---|---|---|---|
| Contact (CRM module) | Customer1:1 | Fully supported | |
| Company (CRM module) | Customer / Organization1:1 | Fully supported | |
| Deal (CRM module) | Opportunity (CR302000)1:1 | Fully supported | |
| Pipeline / Pipeline Stage | Opportunity Stage1:1 | Fully supported | |
| Employee (HRM module) | Customer / Contact1:many | Fully supported | |
| Department (HRM module) | Custom field on Contact / Branch1:1 | Fully supported | |
| Pay Grade / Job Title | Custom field on Customer1:1 | Fully supported | |
| Chart of Accounts (Accounting module) | GL Account (GL202000)1:1 | Fully supported | |
| Invoice (Accounting module) | AR Invoice (AR301000)1:1 | Fully supported | |
| Vendor / Payee | Vendor (AP303000)1:1 | Fully supported | |
| Note / Activity | Note / Activity (CR306020)1:1 | Fully supported | |
| Workflow / Automation | No equivalent — rebuild required1:1 | Fully supported | |
| Custom Field (Custom Field Builder extension) | Custom field (entity.custom)1:1 | Fully supported | |
| WooCommerce Order (via WooCommerce CRM integration) | Sales Order (SO301000)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.
WP ERP gotchas
Custom database tables require direct SQL extraction
PHP version and WordPress version mismatches block migration tooling
WooCommerce CRM integration creates duplicate contact records
Payroll historical data is module-gated and extension-specific
Workflow automation rules are serialized PHP in wp_options
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 WP ERP data via REST API and direct database access
FlitStack connects to your WP ERP instance using scoped read credentials that access both the WordPress REST API endpoints for CRM contacts and companies and direct database reads from wp_erp_hr_employee, wp_erp_acct_invoices, wp_erp_custom_fields_meta, and related tables. We use parameterized queries to extract the full dataset without modifying your WP ERP installation. The extraction runs in a sandboxed read-only session. All WP ERP data is exported as structured JSON with original timestamps, owner IDs, and custom field values intact.
Map WP ERP entities to Acumatica screens and schema
We build a migration schema that assigns each WP ERP object (Contact, Company, Deal, Employee, GL Account, Invoice) to its Acumatica destination screen and field. Custom fields created in WP ERP's Custom Field Builder are deserialized from PHP format and mapped to Acumatica custom fields on the appropriate entity. For multi-entity Acumatica setups, we create a branch-mapping specification that assigns WP ERP records to the correct Acumatica company. This schema is reviewed with your Acumatica admin before any data moves.
Load master data and GL accounts before transactional records
Acumatica enforces referential integrity — Customers must exist before Opportunities, Vendors before AP Invoices, and GL Accounts before any transaction can post. We sequence the migration load in dependency order: first the chart of accounts and GL segment definitions, then Customer Classes and industry codes, then Customer and Vendor master records, then Opportunities and AR/AP documents, and finally Activities and Notes. Each batch is validated against Acumatica's screen-level constraints before the next batch begins. Employee records are loaded last and classified as Users, Customers, or Contacts per your team's specification.
Run sample migration with field-level diff against Acumatica test tenant
We migrate a representative sample of 50–200 records spanning contacts, companies, deals, employees, and GL accounts into an Acumatica test environment. We generate a field-level diff comparing each source field against the destination field value. You review the diff to confirm that WP ERP lifecycle stages landed in the correct Acumatica custom fields, GL account codes resolved to the right account records, and employee classification matched your specification. Sample validation is the gate before the full migration runs.
Execute full migration with delta-pickup window
The full migration loads all WP ERP records into Acumatica production using Acumatica's REST API endpoint (Default/23.200.001). A delta-pickup window of 24–48 hours captures any WP ERP records created or modified during the cutover period so Acumatica reflects your final WP ERP state. Every operation is logged in an audit trail. If post-migration reconciliation reveals missing records or data integrity issues, FlitStack provides a one-click rollback that restores Acumatica to its pre-migration state without affecting your WP ERP instance.
Platform deep dives
WP 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 WP 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
WP ERP: WordPress REST API with no publicly documented rate limit; XML-RPC is capped at 10 requests per 30 seconds per IP on VIP environments.
Data volume sensitivity
WP 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 WP ERP to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your WP 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 WP 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.