Migrate from Iptor ERP to Microsoft Dynamics 365 Business Central

Iptor's unified Business Partner entity covers both customers and vendors with a BP type field. We split on BP type during migration: BP type Customer maps to Dynamics 365 Customer card with Customer Posting Group; BP type Vendor maps to Vendor card with Vendor Posting Group. Address book entries, contact information, and payment terms transfer to the respective card. Custom fields on the BP record attach as custom fields on the Customer or Vendor.

Iptor Items with configurable attributes, Item Classifications, and multiple unit-of-measure settings migrate to Dynamics 365 Item cards. The Item Type (Inventory, Service, Non-inventory) is set based on Iptor's stock control flag. Item Classification hierarchies are flattened to a primary Category with additional classification levels stored as Item Attributes or as a custom category hierarchy table depending on the Dynamics edition. Unit-of-measure conversions map to the Dynamics 365 Unit of Measure setup.

Iptor Sales Orders migrate as Microsoft Dynamics 365 Sales Order drafts. Order number, order date, required delivery date, and customer reference map directly. Sales lines transfer with item number, quantity, unit price, line discount, and warehouse location. Open versus fulfilled status determines whether the order remains in draft or is posted and closed. Partially fulfilled lines are flagged with shipped versus ordered quantities.

Iptor Purchase Orders migrate as Dynamics 365 Purchase Order drafts. Vendor assignment, expected delivery date, and line quantities transfer directly. Partially received POs are migrated with received quantities flagged and remaining quantities as open lines. Iptor's approval workflow status does not transfer; the customer re-applies approval routing in Dynamics 365 post-migration.

Iptor Delivery Notes map to Dynamics 365 Posted Sales Shipments. Header details (delivery number, date, customer, shipping address) and line details (item, quantity shipped, unit of measure, warehouse) transfer directly. The original Sales Order reference is preserved as a linked document for audit trail. Picked versus shipped quantities are reconciled during migration.

Iptor AR invoices migrate to Dynamics 365 Posted Sales Invoices. Invoice number, invoice date, due date, payment terms, and tax jurisdiction codes map to the posted invoice. Line items, amounts, and tax amounts transfer with invoice-level and line-level VAT or sales tax codes resolved to the destination tax setup. Open invoices remain open; paid invoices are posted as paid with payment journal entries.

Iptor AP invoices migrate to Dynamics 365 Posted Purchase Invoices. Vendor invoice number, invoice date, due date, and payment terms transfer. Line items and amounts map with vendor-specific posting groups assigned. Tax codes are resolved to the Dynamics 365 tax configuration. Open payables are migrated as open posted invoices with outstanding amounts reconciled against the vendor ledger.

We extract open payables and receivables as explicit ledger entries at migration time so the destination begins with an accurate aged trial balance. Each open AR invoice generates a Customer Ledger Entry with remaining amount; each open AP invoice generates a Vendor Ledger Entry with remaining amount. Closed items migrate as historical records for reporting continuity. This requires a dedicated migration step just before go-live to capture the latest balances.

Iptor's configurable segment-based account structure maps to Dynamics 365 Main Accounts with financial dimensions. Each Iptor account segment maps to a Main Account number or to a financial dimension value depending on the segment's function. Accounts with non-standard segment assignments are flagged for manual review before migration. We preserve the full account hierarchy and map Iptor's account type (Income, Expense, Asset, Liability, Equity) to the Dynamics 365 Main Account Category.

Stock levels, warehouse locations, and lot/serial numbers migrate as current-state snapshots at go-live. Iptor's multi-warehouse setup requires mapping warehouse codes to Dynamics 365 Location codes. Open item ledger entries for in-transit inventory are migrated with warehouse assignments. Lot and serial number traceability records transfer to Dynamics 365 item tracking entries with expiration dates preserved.

Historical journal entries are migrated for reporting continuity. Iptor's journal types including recurring entries map to Dynamics 365 General Journal with the original journal date, description, and all debit/credit line amounts preserved. Balancing account assignments are resolved through the account mapping table. We do not migrate locked or posted periods; only open and recent posted entries transfer.

Only present where the Iptor Publishing module is active. Royalties, Rights, Permissions, and Contract records use a multi-dimensional structure that has no native Dynamics 365 equivalent. We convert these records to a flattened schema with fields for contract ID, right type, royalty rate, entitlement period, counterparty, and payment terms. The customer reviews and approves the flattened schema before we commit. If Dynamics 365 Finance and Operations is the destination, custom tables can store this data natively; for Business Central, we deliver structured CSV with field mapping documentation.

User accounts, passwords, and role assignments do not migrate directly due to identity and security constraints. We extract the user list and role assignments from Iptor and produce a User Mapping Table that the customer's Dynamics 365 admin uses to provision corresponding users in Azure AD and assign permission sets. Inactive Iptor users are flagged for optional provisioning.

Documents stored in Iptor's document management system are exported as a file package with folder structure preserved. Each file is associated with the related transactional or master record and delivered as a zipped archive alongside the migrated data. The customer uploads the archive to Dynamics 365 SharePoint or OneDrive integration post-migration.