Migrate from IS Packaging to Microsoft Dynamics 365 Business Central

IS Packaging Items (item number, description, unit of measure, category, costing layers, and custom properties) map to Business Central Item records. The Item No. is the primary key; we preserve any supplier item cross-references as Item Vendor Catalog records in Business Central. Custom fields on Item require pre-creation of the matching Business Central custom field (table extension) before migration data loads.

Each IS Packaging BOM revision (revision number, effective date, component lines with quantities, routing steps, and phantom assembly flags) splits into a Business Central Production BOM header and one or more BOM Version records keyed by starting date. We build a revision cross-reference table during discovery that maps each IS Packaging revision number and effective date to the corresponding Business Central BOM Version starting date and status. Phantom assemblies migrate as BOM lines with the Phantom field set; routing operations migrate to the BOM Version Routing Lines tab with work center codes resolved against the work center master created during schema setup.

IS Packaging Production Orders (linked to a BOM revision, scheduled quantity, plant, and work center with current status and completion percentage) map to Business Central Production Order. The IS Packaging status (Created, Released, In Process, Closed) maps to Business Central Status (Registered, Released, Finished, Stopped) via a status mapping matrix built during discovery. Partial completion percentages from IS Packaging translate to posted output journal quantities in Business Central; we compute the equivalent output quantity before import so that work in progress carries forward.

IS Packaging Work Orders tied to Production Orders with scheduling, labor hours, and machine time map to Production Order Routing Lines and Capacity Ledger Entries in Business Central. Routing line sequence, work center code, setup time, and run time migrate as routing data. Actual labor and machine time from IS Packaging become capacity entries posted against the routing. If IS Packaging uses plant-specific work center codes, we map them to Business Central Work Center codes during schema design.

IS Packaging Finished Goods Location records tied to Items with lot/serial tracking and on-hand quantities map to Business Central Location codes paired with Item Tracking Lines. We extract location names, bin structures, and on-hand balances by item and lot, then create Location records in Business Central with the appropriate warehouse class. On-hand balances load as positive inventory adjustment journals at cutover. If IS Packaging uses bin locations, we create the corresponding bin codes in Business Central warehouse setup.

Lot and serial number formats in IS Packaging vary by plant (date-coded, supplier-prefixed, or sequence-based). We extract the raw lot identifiers and metadata from IS Packaging inventory transactions, normalize them into a unified format, and re-associate them against Business Central Item Tracking Code setup. Lot transactions (receipts, issues, adjustments) become Item Ledger Entries with the normalized lot number. We build a lot cross-reference table during discovery that records the original plant-specific lot identifier and its normalized Business Central equivalent for traceability continuity.

IS Packaging inventory transaction history (receipts, issues, adjustments) maps to Business Central Item Ledger Entries and Value Entries. Large transaction volumes require chunked extraction in chronological order to preserve inventory cost rollup. We chunk by date range (typically monthly batches) and load via Business Central API or rapid data migration tools, applying the same lot number normalization used for live inventory. Cost layer integrity is maintained by loading Value Entries after Item Ledger Entries with matching posting dates.

Open IS Packaging Customer Orders with headers (customer number, order date, terms, shipping address) and line items (item number, quantity, unit price, discounts) map to Business Central Sales Order and Sales Line records. We extract all open orders, flag pricing exceptions for manual review before import, and load orders in Sales & Receivables setup. If IS Packaging uses custom pricing rules or uom conversions, we document these in the pricing exception report and advise the customer to configure the equivalent Business Central sales pricing and discount structures post-migration.

IS Packaging Vendor masters (vendor number, name, contact, payment terms, item-supplier cross-references) map to Business Central Vendor. Vendor-to-item cross-references migrate as Item Vendor Catalog entries linking the Business Central Item to the vendor and supplier item number. Payment terms and shipping instructions map to Business Central Vendor Payment Terms and Location codes.

IS Packaging Chart of Accounts maps to Business Central G/L Account structure. We extract account codes, descriptions, and account types, then map them to Business Central G/L Account numbers with the same segment structure. If the destination Business Central instance uses a different account segment scheme (e.g., adding a cost center dimension), we flag inactive accounts for reactivation and intercompany accounts for review before import. Account balances from IS Packaging load as General Journal lines with opening balances in Business Central.

Custom fields added to standard IS Packaging objects (Item, BOM, Production Order, Customer Order, Vendor) are inventoried by name, data type, and values during discovery. We pre-create the matching Business Central table extensions (field group, type, and length matching the IS Packaging definition) before any data import. Values load as standard field data after the table extension is deployed. Custom fields with picklist or enumerated values require corresponding option fields or related tables in Business Central.

IS Packaging MRP pegging records that tie customer demand to specific production orders have no direct Business Central equivalent; MRP in Business Central generates requisition lines and production forecasts rather than storing pegging relationships. We extract the pegging data as a reference report during discovery and deliver it as a written document that the customer's production planner uses to manually restore demand linkages in Business Central's Planning Worksheet after go-live. This is a manual handoff, not an automated import.