Migrate from iXERP Standard to Microsoft Dynamics 365 Business Central

iXERP Customer records include company details and individual contact fields in a single record. We split these into a Dynamics 365 Account (company-level data including billing address, payment terms, and credit limit) and a Contact record (individual contact fields including name, email, phone, and role). The Account is created first so that Contact.accountId is satisfied at insert time. Outstanding invoice balances and credit limits migrate as Account-level financial fields.

iXERP Vendor records map directly to Dynamics 365 Finance Vendor. We preserve vendor name, address, payment terms, and accounts payable balance. If multiple iXERP Vendor records share the same name (duplicate suppliers), we flag these during pre-flight and apply a dedupe strategy before loading to avoid duplicate Vendor accounts in Dynamics 365.

iXERP Items (inventory SKUs, non-stock items, and services) map to Dynamics 365 Supply Chain Management Product2 with Released Product configuration. Item codes, cost prices, selling prices, and stock-on-hand quantities migrate directly. Serial and batch tracking fields map to Tracking Dimension groups in Supply Chain Management if those features are active in iXERP. Unit of Measure from iXERP maps to a Unit of Measure Group in Dynamics 365.

iXERP Purchase Orders with header-level details (vendor reference, order date, delivery date, status) and line items (item, quantity, unit cost, line total) map directly to Dynamics 365 Finance Purchase Order. PO status values from iXERP (Draft, Sent, Received, Closed) map to corresponding Procurement statuses in Dynamics 365. We import open and partially received POs; fully received and closed POs are migrated as historical records with a Closed status.

iXERP Sales Orders map to Dynamics 365 Supply Chain Management Sales Order with header fields (customer account, order date, shipping address, payment terms) and line items (product, quantity, unit price, discount). Fulfilment status from iXERP maps to the Dynamics 365 Status field, and related Invoice references carry forward as linked Invoice IDs. Open sales orders migrate with their fulfillment progress preserved so that partially shipped orders can be completed post-migration.

iXERP Issues Invoices (accounts receivable) map to Dynamics 365 Finance Customer Invoice and Receipts Invoices (accounts payable) map to Vendor Invoice. Multi-line detail, tax codes, and payment status migrate directly. Invoices that are fully paid carry a Closed status with payment reference preserved; unpaid invoices carry the outstanding balance against the Customer or Vendor account. We flag any iXERP invoice types that do not have a clear Dynamics 365 equivalent during the mapping phase for customer decision.

iXERP Project records map to Dynamics 365 Project Service Automation or Dataverse Projects depending on the licensed module. Project headers, assigned resources, milestone dates, and custom project fields migrate directly. The task hierarchy migrates as Project Tasks with parent-child relationships preserved. Time entries and budget fields map to the Project time and budget entities. If Project Service Automation is not licensed in the destination, we migrate Projects to Dataverse and flag the constraint.

iXERP Tasks belonging to Projects migrate as Project Tasks in Dynamics 365. Each task retains its project association via the projectId lookup, preserving the task hierarchy. Assignee, status, hours logged, and custom task fields migrate directly. Tasks without a project association migrate as generic Project Tasks under a default migration project.

iXERP Employee records (personal details, job roles, departments, and compensation fields) map to Dynamics 365 Human Resources Worker or Dataverse HR Worker depending on the licensed module. Effective-dated employment fields and multi-address records require careful mapping to the Worker's employment relationship entity. We detect all custom HR property names during the profiling phase and map them to matching destination fields or store them as extended attributes. HR module availability in the destination must be confirmed before migration.

iXERP document attachments are stored as URL references to external cloud storage providers, not as binary blobs. We migrate the URL references but not the files themselves. Post-migration, the customer must validate that all URL references remain accessible and update any that point to decommissioned storage endpoints. This limitation is documented in the migration scope and flagged as a post-migration action item for the customer.

iXERP Bank and Cash account balances and transaction histories migrate to Dynamics 365 Finance Bank Account. Opening balances carry across, and we flag any gaps in historical transaction detail caused by date-scoped truncation. Reconciliation data migrates where the transaction dates allow.

The iXERP general ledger account codes, names, and classifications map to the Dynamics 365 Finance Chart of Accounts. Account types and tax codes translate to the destination account type and sales tax group equivalents. Custom segment structures in iXERP (such as cost-centre or department coding in the account code) map to Financial Dimensions in Dynamics 365, which must be designed and configured before the ledger migration. This work requires coordination with the customer's finance team during the pre-migration design phase.

iXERP stock movements, adjustments, and transfers migrate to Dynamics 365 Supply Chain Management inventory journal lines. Historical transaction volume can be very large; we scope the migration by date range and flag any truncation required due to destination data volume constraints. Inventory dimensions (site, warehouse, location, batch, serial) from iXERP map to the corresponding Inventory Dimension groups in Dynamics 365 Supply Chain Management.

iXERP HelpDesk tickets with customer reference, agent assignment, status, and conversation history map to Dynamics 365 Customer Service Case. Ticket pipeline stages map to Case Status values, and conversation threads migrate as Case Activities linked to the Case. Custom ticket fields carry across as Case-level extended attributes. If Customer Service is not licensed in the destination, we migrate tickets as notes attached to the relevant Account or Contact.