Migrate your iXERP Standard data

Customer records are standard master-data objects with contact fields, addresses, and financial balances. We export and import Customer records via the API or CSV templates, preserving outstanding invoice references and credit terms.

Vendor master records hold supplier details, payment terms, and accounts payable balances. We map vendor records 1:1 and flag any duplicate vendor names during the pre-flight check.

Items represent inventory SKUs, non-stock items, and services. We preserve item codes, cost prices, selling prices, and stock-on-hand quantities. Serial and batch tracking fields are carried across if configured.

Purchase Orders track buy-side commitments with line items, quantities, and received-to-date values. We import open PO headers and lines, mapping status fields to the destination system's equivalents.

Sales Orders hold customer-facing commitments with line items, pricing, and fulfilment status. We migrate open and historical Sales Orders including fulfilment progress and related Invoice references.

iXERP Issues and Receipts Invoices carry multi-line detail, tax codes, and payment status. Mappings between iXERP invoice types and destination invoice objects must be agreed upfront because naming conventions vary across platforms.

Projects group tasks, time entries, and budgets. We migrate project headers, assigned resources, and associated task hierarchies, preserving milestone dates and custom project fields.

Tasks belong to Projects and carry assignees, status, and hours logged. We preserve the task-to-project relationship and carry across time-entry associations.

HR Employees include personal details, job roles, departments, and compensation fields. We map Employees to the destination HRMS schema, handling effective-dated fields and multi-address records carefully.

Document attachments are stored as URL or hyperlink references to external cloud storage rather than as binary blobs within iXERP. We migrate the document links but not the files themselves; the destination system must have equivalent storage configured.

iXERP supports custom fields across CRM and HR modules. We detect all custom property names and values during the profiling phase and map them to matching destination fields or store them as extended properties.

Bank and cash account balances and transaction histories are migratable. We carry across opening balances, reconcile data where dates allow, and flag gaps in historical transaction detail.

The general ledger structure with account codes, names, and classifications migrates cleanly. We map account types and tax codes to destination equivalents during the transformation phase.

Stock movements, adjustments, and transfers are recorded as inventory transactions. Historical transaction volume can be large; we scope migration by date range and flag any truncation needed due to destination system limits.

HelpDesk tickets carry customer references, agents, status, and conversation history. We migrate ticket headers and associated conversation threads, preserving agent assignment and custom ticket fields.