Migrate from INNERGY ERP to Microsoft Dynamics 365 Business Central

INNERGY Customer records map to Dynamics 365 Customer with contact details, billing and shipping addresses, and the associated Jobs list preserved. Dynamics 365 uses a three-partner model: Customer and Vendor are separate records, but a Contact record links to both. We map INNERGY Customer to the Dynamics Account (for billing relationships) and create associated Contact records for individual points of communication. Division-specific naming conventions identified during schema audit are normalized to Dynamics naming standards.

INNERGY Vendor records map directly to Dynamics 365 Vendor with supplier information, lead times, and preferred items. We preserve any associated purchase history exposed through INNERGY's API as a linked table rather than collapsing it into the Vendor record, so the customer's AP team retains reference to historical PO data. Vendors without a matching Dynamics entity are held in a reconciliation queue for the customer's admin to validate before final import.

INNERGY Estimates map to Microsoft Dynamics 365 Sales Quote. The full estimate structure — material takeoffs, labor assumptions, margin calculation, and line item detail — migrates to Quote Lines. INNERGY's estimate status (Draft, Sent, Accepted, Lost) maps to Dynamics Quote Status with the original estimate number preserved as a reference field for audit. If the customer uses Dynamics Project Operations, Estimates can alternatively map to Opportunities with Estimates, depending on the configured sales flow.

INNERGY Jobs are the core project record tracking from award through installation. We map Jobs to Dynamics 365 Projects with job costing enabled (using the Project Management and Accounting module in Finance & Operations or the Jobs extension in Business Central). The Job number becomes the Project ID, and the Job status history migrates as Project Stage records. If the customer's workflow uses sales orders to drive production, we also create Sales Orders linked to the Project for billing purposes.

INNERGY BOMs auto-generated from CAD data or built manually include material specs, quantities, operations routing, and subassembly relationships. CAD-derived BOMs require manual reconstruction in Dynamics 365 because the platform does not have a native CAD geometry-to-BOM importer. We export the INNERGY BOM structure including all components, quantities, operations, and routing, then map to Dynamics Manufacturing BOMs or Item BOMs depending on whether the destination uses Production Orders or standard item manufacturing. Multi-level BOMs are rebuilt as nested Production BOM structures in Dynamics with routing steps mapped to Work Centers.

INNERGY Work Orders drive shop-floor execution and are linked to Jobs and BOMs. We map Work Order records to Dynamics 365 Production Orders including assigned operations, sequencing, and completion status. The Work Order number becomes the Production Order number, and the linked Job reference is preserved as a Project association on the Production Order. Operation sequence and workstation assignments migrate to Production Order Routes.

INNERGY Change Orders modify the scope of an active Job and track lineage, approval dates, and revised quantities. We preserve change orders as a structured linked table rather than collapsing them into the Job record. In Dynamics 365, Change Orders map to Project Modification records (Finance & Operations) or Sales Order modifications (Business Central) linked to the parent Project or Sales Order. The change order sequence and original Job number are preserved as metadata for audit and project costing.

INNERGY tracks material and component inventory with units of measure, reorder points, and warehouse locations. We map inventory balances, average costs, and stock statuses to Dynamics 365 Items with the appropriate Item type (Stockkeeping, Non-Stock, Service). INNERGY warehouse locations map to Dynamics Locations, and lot and serial tracking settings migrate to the corresponding inventory dimension groups. If INNERGY uses multi-site inventory, we configure Sites and Locations in Dynamics to match before inventory quantities are written.

INNERGY supports custom fields on key objects, and Feature Release 115 added custom fields for Shipments. Custom fields are user-defined and may not follow a stable naming schema. We catalog all custom fields during schema audit, map each to a typed Dynamics 365 extension field (Text, Decimal, Integer, Boolean, Date, Option), and deploy the extension schema into the destination environment before any data import. Any orphaned or mislabeled custom properties identified during API discovery are flagged in the pre-migration report.

INNERGY integrates accounting data through the ERP module with account structures configured per-customer during implementation. We export the full account list and map it to Dynamics 365 Chart of Accounts with account type, posting definitions, and any dimension structures (Department, Division, Cost Center) preserved. INNERGY division-specific cost pools map to Dynamics Financial Dimensions, which must be configured before any transactional data is imported.

Outstanding invoices and credit memos represent live financial data that must be reconciled before migration to avoid double-counting. INNERGY exposes open payable and receivable records through its API. We extract open AP and AR items, reconcile outstanding balances against bank statements before migration, and post them to Dynamics 365 as open invoices rather than paid records so that the AP and AR teams can continue reconciliation in the destination system. Closed historical transactions are exported as a reference table attached to the relevant Account.

INNERGY stores documents and drawings associated with Jobs, Work Orders, and Estimates, including PDFs, images, and CAD files. We export attachments in their native format and link them to the corresponding Dynamics 365 records via SharePoint integration or Microsoft OneDrive for Business. CAD files (DXF, DWG) are preserved as-is; PDFs and images attach to the relevant Project, Item, or Production Order record. The original attachment folder structure is replicated in SharePoint for discoverability.