Migrate from WP ERP to Microsoft Dynamics 365 Business Central

WP ERP stores HR employees in erp_hr_employees with a wp_user_id foreign key linking to wp_users and wp_usermeta. We extract personal details (name, email, phone, address), employment status, department_id, job_title, hire_date, and compensation fields, then normalize WordPress user meta into Worker record fields in Dynamics 365 Human Resources or Business Central HCM. WordPress roles do not map directly to Dynamics 365 Worker roles; we assign the default Worker position and flag any compensation or benefits data for manual HR admin review before finalization.

WP ERP stores departments in erp_hr_departments as flat key-value records with parent_id for hierarchy. We extract the full department tree, preserve parent-child relationships, and map to Dynamics 365 Business Units (hierarchical organizational units) or Departments depending on the destination edition. We reattach employees to the correct department reference during Worker migration by resolving the department_id foreign key.

Leave requests in erp_hr_leave_requests (approved, rejected, pending) migrate to Dynamics 365 HCM Leave Request records. Leave type, start date, end date, status, and approved-by user cross-reference are all mapped. Pending leave requests at migration cutover are flagged for the HR admin to approve in the destination system since workflow-triggered notifications cannot be carried over.

WP ERP CRM contacts in erp_crm_contacts include name, email, phone, address, social profiles, lifecycle_stage, source, and owner_id. We extract all standard fields plus custom fields built with the Custom Field Builder extension, map lifecycle_stage to a custom Contact field for post-migration segmentation, and set the contact's primary address from erp_crm_contact_addresses. If WooCommerce CRM integration created duplicate contacts for the same email address, we detect these during scoping and present a merge decision to the customer before export.

WP ERP company records in erp_crm_companies link to contacts via erp_crm_contact_relations. We preserve the company-contact association mapping during migration, extract the company name, domain, address, and industry, and create Salesforce-style Account records in Dynamics 365 with the company-domain mapped to Website. After creating Accounts, we reattach Contact records by resolving the erp_crm_contact_relations mapping to the new Account GUID.

Deals (CRM Deals extension, $9.49/mo) store deal title, value, currency, stage, owner, and pipeline association in erp_crm_deals. We map deal title to Opportunity.Name, deal value to Amount, currency to TransactionCurrencyId, and stage to a Dynamics 365 Opportunity Stage that we configure as a Sales Process before migration. Pipeline stages differ between WP ERP and Dynamics 365; we provide a stage mapping worksheet during scoping and apply it during the transform phase. Owner resolution uses the email-based user lookup established in the Owner mapping step.

Activities (calls, meetings, tasks, emails) stored in erp_crm_activities with polymorphic type fields (type: call, meeting, email, task) are flattened into Dynamics 365 activity records. Call dispositions and durations land in custom Task fields. Meeting start and end times map to Appointment StartTime and EndTime. Activity timestamp is preserved in the ActivityDate or DateCreated field. Activities without a resolved parent Contact or Company are attached to the owning Contact or Account record identified during the entity-resolution phase.

WP ERP Accounting stores the chart of accounts in erp_ac_chart_of_accounts with account code, name, type, and subtype. We preserve the full account structure including parent-child relationships for grouped accounts, map account type to the Dynamics 365 G/L Account Type (Posting, Heading, Total, or statistical), and set the appropriate account category. The account code becomes G/L Account Number; we validate that codes are alphanumeric and within the Dynamics 365 character limit before import.

Accounting customers in erp_ac_customers link to CRM contacts via erp_crm_contacts.id. We resolve this cross-reference during migration so that each customer record in Dynamics 365 is linked to the corresponding Account record created from the CRM Company. The customer name, billing address, and payment terms are mapped; if no corresponding CRM Company exists for an erp_ac_customer, we create a standalone Customer record without an Account linkage.

Vendor records in erp_ac_vendors (vendor name, billing address, contact email) migrate to Dynamics 365 Vendor records. Vendor-ledger entries link via the vendor_id foreign key and are resolved after the Vendor records are created. We map payment terms and currency from WP ERP vendor fields to Dynamics 365 Vendor payment terms and TransactionCurrencyId.

WP ERP invoices in erp_ac_invoices include line items, tax codes, payment status, and due dates. We flag open invoices versus paid or voided invoices and map invoice status to the Dynamics 365 equivalent (Open, Paid, Cancelled). Open invoices are migrated as active receivables linked to the Customer and Account; paid and voided invoices migrate with their final status and are available for historical reporting. We do not regenerate PDF invoices; we archive invoice metadata as document attachment records.

Manual journal entries in erp_ac_journal_entries migrate to Dynamics 365 General Journal lines with debit and credit amounts mapped to the corresponding G/L Account. We resolve COA account references from the chart of accounts mapping so that each journal line debits or credits the correct account number. Automated payroll journal entries (generated by the Payroll extension) are migrated as separate journal batches with a Payroll source reference. Journal entry dates and descriptions are preserved.

Payroll is a $9.49/month extension. Historical payslip data in erp_hr_payroll* tables is included in standard HRM extraction. We migrate payslip metadata (pay period, gross pay, deductions, net pay, tax withholdings, bank transfer data) as Worker Compensation history or Pay Statement records if the destination HCM supports it. If the destination is Business Central without the full HCM add-on, payroll history migrates as a custom payroll-history table with a flat record structure. Payslip PDFs require regeneration on the destination system.

When WP ERP's WooCommerce CRM integration is active, WooCommerce order customers create CRM contact records automatically. These records carry a WooCommerce order ID reference in erp_crm_contacts. We extract these separately, map the contact to a Dynamics 365 Contact, link to the corresponding Account, and carry the original WooCommerce order reference in a custom field for any future WooCommerce-Dynamics integration rebuild.