Migrate from Open-Prod to Microsoft Dynamics 365 Business Central

Open-Prod customer records map to Dynamics 365 Customer entities. Business Central uses a single Customer card; Finance and Operations distinguishes between Customer and CustTable. We extract customer name, addresses (all locations), payment terms, tax registration number, currency, and credit limit. Address handling is critical: Open-Prod allows multiple address records each with an independent primary flag, while Dynamics 365 allows multiple address purposes (Invoice, Delivery, etc.) with only one address per purpose type. We require business-user validation during scoping to confirm how address data should be restructured.

Open-Prod vendor records map to Dynamics 365 Vendor entities. We extract vendor name, addresses, payment terms, tax ID, currency, and GL bank account. Like customers, address restructuring must be validated against Dynamics 365's address purpose model before migration. Vendors without a matching tax registration in the destination country/region configuration require a new tax group setup.

Open-Prod item records map to Dynamics 365 Item (Inventory) or Product (non-inventory) entities. We extract item number, description, unit of measure, item category, product type (Stock, Service, Non-stock), base cost, and sales/purchase prices. Item variants in Open-Prod (size, color, configuration) map to Dynamics 365 product dimensions. Product dimensions must be configured in the destination before item import so that the variant records have a valid parent.

Open-Prod inventory quantities by warehouse map to Dynamics 365 Item Tracking entries or warehouse journal lines. We extract on-hand quantities per item per location. Open purchase orders, pending receipts, and work orders require sequencing: these must be migrated after inventory is established to avoid stock discrepancies. Bin and lot tracking settings in Open-Prod must be translated to Dynamics 365 item tracking configuration (None, Serial, Lot, or Package) before inventory loads.

Open-Prod sales documents map to Microsoft Dynamics 365 Sales Orders and/or Sales Invoice records depending on Open-Prod document status. We preserve document number, customer reference, order date, line items (item, quantity, unit price, discount), taxes, and totals. Open (unfulfilled) orders migrate as open Sales Orders; invoiced documents migrate as posted Sales Invoices. Document numbering series must be pre-configured in Dynamics 365 to accept the Open-Prod document number range without conflict.

Open-Prod purchase orders map to Dynamics 365 Purchase Orders. We extract vendor reference, order date, line items, quantities, costs, and taxes. Open purchase orders migrate as unposted Purchase Orders with the appropriate status. Purchase invoice records migrate as posted purchase invoices. GL account distribution on purchase lines requires mapping Open-Prod expenditure posting accounts to the Dynamics 365 chart of accounts.

Open-Prod general ledger accounts map to Dynamics 365 G/L Account (Business Central) or MainAccount (Finance and Operations) with financial dimension support. We extract account number, name, type, and posting group. For Finance and Operations destinations, we also configure the financial dimension framework and map any Open-Prod cost center or department codes to the corresponding Dynamics 365 dimension structure. GIFI code mapping applies for Canadian destinations. This module must be complete before any transactional record migration because all sales, purchase, and inventory documents post to G/L accounts.

Open-Prod project records map to Dynamics 365 Projects with WBS (Work Breakdown Structure) task hierarchies preserved as project tasks. We extract project number, name, status, responsible user, dates, budget amounts, and task lines. Project type mapping (Time and Material vs Fixed Price) must be confirmed during scoping. Hourly cost rates and billable prices from Open-Prod migrate to project price lines. Project contracts migrate as project customer associations or as project billing rules depending on destination module.

Open-Prod service ticket records map to Dynamics 365 Service Management objects. In Business Central, service orders and service item registration are the primary service objects; in Finance and Operations with Field Service, cases and work orders are the equivalent. We extract ticket number, customer, item under service, problem description, status, priority, technician assignment, and resolution notes. Service contract records migrate as service agreement or subscription billing entities if the destination supports them.

Open-Prod custom fields are not publicly documented in a machine-readable schema, which prevents automated field-level mapping. We perform a configuration review during scoping to enumerate all observed custom fields in the customer's instance, classify them by object and data type, and recommend the equivalent Dynamics 365 custom field implementation. We cannot guarantee that every custom field will map automatically; any unmappable field is flagged in the scoping document for the customer's admin to review post-migration. Custom field data migration requires a custom mapping document per field.

Open-Prod stores attachments within records, but we have not confirmed a public file-attachment export mechanism through the Open-Prod API. Attachments and embedded files are out of scope for standard migration. We flag this gap in the scoping document. If the customer has a documented export procedure for attachments (e.g., database-level access to the Open-Prod file store), we can assess it as an add-on scope item. Without a confirmed export path, attachments remain in Open-Prod as a read-only archive post-migration.

Open-Prod currency and tax posting settings map to Dynamics 365 Currency, Tax Group, and Tax Setup entities. We extract currency codes, exchange rates, tax registration numbers, and tax posting accounts. Multi-currency configurations from Open-Prod translate to Dynamics 365 currency pairs and exchange rate providers. Tax group assignment on customer and vendor cards must be configured before customer and vendor migration so that the correct tax groups are available at import time.