Migrate from Integra ERP to Microsoft Dynamics 365 Business Central

Integra ERP stores a flat account list with type classification (Asset, Liability, Income, Expense) and optional GST registration flags. We map each source account code to a Dynamics 365 MainAccount, preserving the original account number as the MainAccount ID and the account name as DisplayName. We configure AccountType, AccountCategory, and any GST-related posting definitions from source account flags. If the source uses cost-center sub-accounts, we implement Dynamics 365 Financial Dimensions (Department, Cost Center, Project) as separate dimension sets rather than embedding segments in the account code.

Customer records including contact details, billing addresses, GST/VAT registration numbers, and credit terms transfer directly to Dynamics 365 CustTable. We map the source customer ID to the destination AccountNum, preserve the payment terms as Dynamics 365 CashDisc and PaymentTermId references, and carry forward any credit limit as the CreditMax on the customer. Open AR balances are extracted as of the migration date and entered as opening-balance transactions in the AR subledger rather than as individual invoices.

Vendor master data maps to Dynamics 365 VendTable, preserving vendor ID, name, address, GST/VAT registration, and payment terms. We transfer vendor-specific item pricing where it exists in the source data as vendor product group records in Dynamics 365. Open AP balances are extracted as of migration date and entered as opening-balance transactions in the AP subledger so that outstanding payable amounts reflect correctly in AP aging reports.

Items carry Integra-specific classification codes, BOM structures for manufacturers, and branch-specific stock values. We flatten BOM hierarchies into individual Released Product records with BOM explosion noted in the product's manufacturing information. We map item type (Stocked, Service, Asset) from Integra's item classification, carry forward the source SKU as the item number, and preserve unit-of-measure definitions. Serial and batch tracking settings transfer to Dynamics 365 inventory dimension groups. Branch-level stock quantities aggregate to destination warehouse or site codes during load.

Integra ERP exports outstanding receivable balances per customer as net amounts. Dynamics 365 does not create individual invoices from the source for historical AR; instead, we create an AR opening-balance transaction using a dedicated Opening Balance journal with CustTrans records of type Opening. We preserve the original invoice reference as free-text invoice numbers and set the due date and amount from the source outstanding balance. This ensures AR aging reports in Dynamics 365 reflect accurate opening positions.

Outstanding payable balances per vendor migrate as AP opening-balance transactions using a dedicated Opening Balance journal in Dynamics 365. We create VendTrans records of type Opening with the vendor account reference, original invoice number, due date, and amount from the source outstanding balance. This reconstructs the AP aging position accurately in Dynamics 365 from the first day of operation.

Open and closed sales orders transfer with line items, pricing, quantities, and order status. We map Integra order-status values to Microsoft Dynamics 365 Sales Status (Backorder, Invoiced, Cancelled). Order lines with items map to SalesLine with ItemId, SalesQty, SalesPrice, and discount percentages. Closed orders are migrated as invoiced sales with the related CustInvoiceJour records so historical revenue reporting is complete. We flag any orders referencing voided customers or discontinued items for customer review before insert.

Stock quantities are branch or warehouse-specific in Integra ERP. We map each source branch to a Dynamics 365 Site and Warehouse combination, and transfer on-hand quantities as InventTrans records of type Opening. Serial and batch numbers transfer to Dynamics 365 InventSerial and InventBatch tables with their associated tracking information. We aggregate by item and warehouse so that Dynamics 365 on-hand reports reflect correct stock positions at go-live.

Employee master records from Integra ERP's employee management module transfer as HcmWorker entities in Finance or Employee records in Business Central. We map employee number, name, department assignment, employment status, and basic compensation fields. Workers map to the Dynamics 365 legal-entity structure and can be assigned to security roles for system access provisioning. Bank account and tax information transfer to HcmWorkerAddress and DirPartyQuantitativeData respectively.

If the source Integra ERP instance uses BOM for manufacturing, we flatten multi-level BOM hierarchies into Dynamics 365 BOMHeader and BOMLine structures. Each Integra BOM at the top level creates a BOM in Dynamics 365 with a version valid for the production site. Component items link to the BOM as BOMLine records with quantity-per relationships. Route and work center definitions do not migrate from Integra and require separate configuration in Dynamics 365 Production.

Attachments, scanned documents, and PDFs stored inside Integra ERP are not exposed via a documented export mechanism. We extract any linked file paths from the source database but cannot guarantee file integrity or completeness. We provide a manifest of document references with their original file paths and associated record IDs, so the customer's admin can manually relocate files to SharePoint or Dynamics 365 Document Handling after migration. No document content migrates automatically.

Integra ERP supports multi-branch deployments where each branch maintains separate inventory, customer, and vendor records. We map each source branch to a separate Dynamics 365 legal entity and assign site codes for inventory dimension segregation. If branches share a single chart of accounts, we configure inter-company accounting in Dynamics 365 so transactions between entities post correctly. Customer and vendor records can be shared across entities or isolated per entity depending on the source data model.