Migrate from WP ERP to Infor CloudSuite Corporate

WP ERP employee records in erp_hr_employees (personal details, employment status, department, job title, hire date, compensation history, WordPress user ID cross-reference) map to Infor CloudSuite HR Employee records. We extract the wp_user_id foreign key to preserve the employee-to-system user link, then map it to the Infor HRM employee identifier. Compensation history (salary, pay frequency, benefit elections) from erp_hr_employees_compensation migrates as HRM pay components in Infor. Note that Infor CloudSuite HRM requires the appropriate CloudSuite edition (typically CloudSuite Industrial or Financials Industrial) and is not included in entry-level CloudSuite Financials deployments.

Department records in erp_hr_departments are key-value structures with parent-child hierarchy. We extract the full department tree and map it to Infor CloudSuite HR organizational units. Employee-to-department assignments migrate as employee organizational assignments linked to the correct department ID. Any department that has no equivalent in Infor CloudSuite's organizational model is flagged for the customer's HR admin to configure post-migration.

WP ERP CRM contacts in erp_crm_contacts (name, email, phone, address, social profiles, lifecycle stage, source attribution, wp_user_id) map to Infor CloudSuite CRM individual records. We preserve the lifecycle stage from erp_crm_contacts.life_stage as a custom attribute in Infor since lifecycle models differ between platforms. If the same email appears in both a manually created CRM contact and a WooCommerce-generated contact (due to WP ERP's WooCommerce CRM integration creating duplicate contact records), we detect these during scoping and give the customer the choice to merge before export.

WP ERP company records in erp_crm_companies link to contacts via erp_crm_contact_relations. We migrate the company record to an Infor CloudSuite CRM Account or Organization and preserve the contact-to-company relationship by resolving the company ID and reattaching the contact lookup in Infor. Billing address, shipping address, company domain, and industry classification migrate as account attributes.

WP ERP activities (calls, meetings, emails, tasks) stored in erp_crm_activities with polymorphic type fields flatten into a standard activity log structure in Infor CloudSuite CRM. We map the activity type, timestamp, body, and owner. Notes attached to contacts or companies migrate as CRM note records linked to the individual or account. The activity sequence is preserved to maintain the customer engagement timeline in Infor.

WP ERP accounting chart of accounts in erp_ac_chart_of_accounts (account code, name, type, subtype, parent-child grouping) maps to Infor CloudSuite Financials COA. We preserve the full account hierarchy including grouped accounts and account type classification (asset, liability, equity, revenue, expense). Note that Infor CloudSuite Financials enforces a specific COA structure per industry edition — accounts must align with Infor's account type codes. If the WP ERP COA uses a non-standard account code scheme, we flag it for restructuring before import.

WP ERP accounting customers in erp_ac_customers link to CRM contacts via erp_crm_contacts.id. We resolve this cross-reference during migration so that invoices land against the correct customer record in Infor CloudSuite Financials. Customer billing address, payment terms, credit limit, and tax ID migrate as customer attributes. If the CRM contact-to-account mapping has not been completed before accounting migration, we hold customer records in a reconciliation queue until the parent record is confirmed.

Vendor records in erp_ac_vendors (company name, billing address, contact email, payment terms) migrate to Infor CloudSuite Financials Vendor. Vendor-ledger entries link via the vendor_id foreign key and migrate as AP transactions in Infor. If the WP ERP vendor uses the same contact record as a CRM company, we merge the accounting vendor with the CRM account record during transformation.

WP ERP invoices in erp_ac_invoices include line items, tax codes, payment status, and due dates. We flag open invoices (status=open) versus paid or voided invoices (status=paid, status=void) and map the invoice status to the equivalent Infor CloudSuite Financials invoice lifecycle state. Open invoices are migrated as unpaid AR records; paid invoices are migrated as historical records with payment reference. Due dates and aging schedules are preserved for customer credit management in Infor.

Manual journal entries in erp_ac_journal_entries (debit/credit line items, account mapping, entry date, description) migrate to Infor CloudSuite Financials journal entries. We map each line item to the corresponding Infor COA account and preserve the debit/credit amounts and entry reference. Automated journal entries generated by the WP ERP Payroll module migrate as payroll journal entries linked to the HR pay run in Infor. Journal entry batch numbering in Infor Financials must follow the customer's configured numbering sequence — we flag any gaps or non-standard formats before import.

Historical payroll records (payslips, tax withholdings, bank transfer data) stored in erp_hr_payroll* tables are available only if the customer purchased the WP ERP Payroll extension ($9.49/month). We extract payslip records as a compliance archive and map pay components (gross pay, deductions, net pay, tax withholdings) to Infor CloudSuite HRM pay history records. Customers must confirm whether payslip PDFs need regeneration in Infor or whether the data archive satisfies their compliance retention requirements.

Inventory is a WP ERP paid extension. We extract item name, SKU, unit cost, current stock quantity, and reorder level from erp_ac_inventory_items. Stock movement history migrates as a separate transaction log. Infor CloudSuite inventory items require a specific item master setup including item group, unit of measure, and warehouse assignment — these must be pre-configured in Infor before item data import because they are prerequisite data that cannot be migrated through the standard import utility.