Migrate from Omni ERP to Microsoft Dynamics 365 Business Central

Omni ERP's account codes (flat or segmented) map to Dynamics 365 Finance's main account structure inside a Legal Entity. We preservecoa numbering and segment count and remap each segment to a corresponding Financial Dimension (such as Department, Cost Center, or Project). Account references in journal entries and AP/AR are updated to point to the new main account ID and dimension combination. If Omni ERP uses a hierarchical segment structure (such as Company-Department-Account), we split each segment into a separate Financial Dimension per the destination's dimensional accounting configuration.

Omni ERP Customer records include contact hierarchies, addresses, and payment terms. Dynamics 365 separates the business entity (Account) from the individual contact (Contact) with a parent-contact relationship. We split Omni ERP Customers into an Account record with the primary contact as a linked Contact record. All address and payment-term fields migrate to the Account; secondary contacts from the hierarchy migrate as additional Contact records linked to the same Account. The original Omni ERP customer number is preserved in a custom field for audit.

Omni ERP Vendor records map to Dynamics 365 Vendor records with the same split logic as Customers: the primary contact becomes a Contact linked to the Vendor, and any additional contacts from the hierarchy are added as related Contact records. Payment terms, tax registration, and W-9/W-8 information migrate to the Vendor record. Vendor bank account details require a separate VendorBankAccount entity in Dynamics 365 Finance and are mapped accordingly.

Omni ERP Items carry serial and batch tracking, multi-warehouse costing, and BOM associations. We export Item records with their costing method (standard, average, FIFO), inventory dimension groups (Site, Warehouse, Location, Batch, Serial), and unit-of-measure conversions. These map to Dynamics 365 Released Product with the corresponding tracking and dimension group configuration applied before the Item is activated in the Legal Entity. Items with lot-level tracking become batch-tracked products; items with serial tracking become serial-tracked products.

Omni ERP BOMs reference finished Items and component Items by code string rather than internal ID. We export the BOM header and lines alongside an explicit Item-code-to-internal-ID mapping table. During import, we resolve every component reference through this mapping before posting the BOM to Dynamics 365. BOM versioning in Omni ERP (stored as a custom property) maps to the Dynamics 365 BOM version entity with effective-from and effective-to dates. If routing data exists, it maps to a Route entity linked to the BOM version.

Open AP invoices in Omni ERP reference Vendor, Chart of Accounts, and Item records. We sequence Vendor import first so that the Vendor account is present before posting AP. Invoice lines map to Vendor Invoice lines with AccountType= Vend and the appropriate main account and financial dimension combination. Prepayments and holds are preserved as invoice status flags. Due dates and payment terms recalculate based on Dynamics 365 payment terms setup unless the original due date is explicitly preserved as a custom field.

Open AR invoices map to Dynamics 365 AR records. We determine whether to import as Free Text Invoice (simple invoicing) or Sales Order (full order management) based on the Omni ERP invoice type flag. Customer and Account lookups are resolved from the Account import. Tax groups in Omni ERP map to Sales Tax Groups in Dynamics 365, and any embedded tax amounts recalculate against the destination tax configuration unless the customer requests exact-amount preservation.

Historical journal entries in Omni ERP reference Chart of Accounts by code and include multi-currency amounts with the exchange rate embedded at the transaction date. We remap account codes to Dynamics 365 main accounts, apply the original transaction-date exchange rate for multi-currency lines (not a standard rate table), and post to the General Journal. Entries that reference a fiscal period closed in Dynamics 365 require the period to be reopened or the entry posted to an adjustment period. Currency variance lines are flagged for manual review if the destination tax or rounding configuration produces a different residual amount.

Fixed Asset records in Omni ERP include acquisition cost, depreciation schedule, and asset category. We map the asset category to a Fixed Asset Group in Dynamics 365 and create a Fixed Asset Book record for each active depreciation method. The original depreciation method is preserved as a custom field if the destination's standard depreciation templates do not match the source schedule exactly. Depreciation run history is not migrated; the asset opens its depreciation schedule from the migration date.

Omni ERP Department and Cost Center records are referenced in journal entries, budget records, and user assignments. We map Departments to Financial Dimensions in Dynamics 365 Finance (such as Department or Cost Center) and create corresponding dimension values with the original Department code and name. If the destination is Dynamics 365 Business Central, Departments map to Dimensions with the same value structure. Circular department assignments in journal entries are flagged during reconciliation and escalated before import.

Omni ERP User records include role assignments and department affiliations. We map roles to the closest Dynamics 365 Security Role by function (such as Accounts Payable Clerk, Inventory Manager, or General Accountant). User email addresses are used as the username in Dynamics 365. Users whose access scope exceeds the destination tier's permission limits are flagged in the reconciliation report for the customer's admin to adjust before the migration cutover.

Omni ERP serial and batch tracking is native to the Item model. We map these to Dynamics 365 Inventory Dimensions by enabling the Batch dimension (for batch-tracked Items) or the Serial dimension (for serial-tracked Items) on the Item's dimension group. On-hand quantity records carry the batch number and expiry date as dimension values. Inventory transactions in Omni ERP that reference a serial or batch number are imported with the corresponding dimension values attached to the inventory transaction lines.

Omni ERP currencies and exchange rate tables map to Dynamics 365 Currency records and Exchange Rate entries. Historical transaction rates embedded in journal entries and AP/AR are applied at the original transaction date during import rather than relying on the destination's rate table. We flag any currency pairs where Omni ERP's rate diverges from the destination's standard rate by more than 1 percent for customer review before the import run commits.

Omni ERP custom fields on Item, Customer, and Vendor objects are captured in the export field checklist and mapped to custom fields in Dynamics 365. In Finance and Operations, we create extension fields via the extension framework or custom fields on the form. In Business Central, we use AL extensions or custom fields on the table. Custom field types (text, integer, decimal, boolean, date) map to their Dynamics 365 equivalents, and we flag any unsupported field types for the customer's admin to review.