Migrate from Info.Net to Microsoft Dynamics 365 Business Central

Info.Net Items (finished goods, raw materials, components) map directly to Dynamics 365 Item records with SKU preserved as item number, description as name, and unit of measure migrated to the Item Unit of Measure table. We flag any Items with no unit of measure defined in Info.Net and default to EACH during migration. Custom fields on Items are pre-created in Dynamics 365 before migration, with custom field API names matched to Info.Net field names and types mapped to equivalent Dynamics 365 field types (text, decimal, integer, Boolean).

Info.Net BOMs define component hierarchies for manufactured Items. We map multi-level BOM structures preserving parent-item links and child-component quantities. Revision versions migrate to BOM Version records linked to the parent Item, with the Active flag set based on the Info.Net revision's current status. Component lines carry the BomItem record type with quantity-per and scrap-percentage preserved from Info.Net. Multi-level BOMs (BOMs within BOMs) require explosion sequencing: we resolve the deepest-level BOM first, then roll upward to preserve the parent-assembly structure.

Info.Net Production Orders track manufacturing jobs with status, quantity, scheduled dates, and assigned work centers. We preserve the full production history including completion dates, actual quantities, and scrap quantities. Production Order status maps to Dynamics 365 status (Simulated, Planned, Firm Planned, Released, In Process, Completed, Stopped). The originating Item and BOM Version are resolved at migration time via the Item and BOM mappings. Work center and operation scheduling data migrate to the production route if routing is defined in the destination.

Info.Net Work Orders assign production tasks to employees or work centers with start/end dates and labor estimates. We map the full work order lifecycle including status transitions and actual labor consumed. Work Order assignment (employee or work center) migrates to the Dynamics 365 Worker or Work Center table respectively. Labor hours and estimated time migrate to the job consumption journal entries in Dynamics 365. If the destination is Business Central, Work Orders may map to the Jobs module depending on whether the customer uses project manufacturing or discrete manufacturing.

Info.Net QC logs hold inspection results, pass/fail flags, and measurement data linked to production lots. Field naming conventions differ between Info.Net and Dynamics 365 Quality Management; we map measurement field names to Dynamics 365 inspection characteristic values and preserve the lot reference linking QC results to the originating Production Order. We flag any QC records with incomplete measurement data as requiring manual verification post-migration. This object is marked as mapping rather than full because Dynamics 365 Quality Management may require separate module licensing (Quality Management is an add-on in some D365 SCM tiers).

Info.Net inventory movements (receipts, issues, adjustments, transfers) carry timestamps, quantities, locations, and cost amounts. We preserve the full transaction ledger with post dates to maintain accurate stock valuation in Dynamics 365. Receipts map to Item Journal lines with entry type Purchase; issues map to Consumption; adjustments map to Positive or Negative Adjustment; transfers map to Transfer Orders with from-location and to-location. Post dates are preserved to maintain G/L posting date continuity for financial reporting.

Info.Net Customer records hold billing addresses, shipping addresses, and credit limits. Dynamics 365 Customer is a party entity with separate Address (Invoice, Delivery, Payment roles) and Contact person records. Multi-address customer accounts require special handling: we extract each address from Info.Net, create separate Address records in Dynamics 365 with the correct role, and assign the primary invoice address and primary delivery address manually if Info.Net distinguishes them. Customer credit limits map to the Dynamics 365 Credit Limit field on the Customer card. Deduplication is applied using Company Registration Number where available, falling back to name and address fuzzy match.

Info.Net Vendor master records include contact details, payment terms, and lead times. As with Customers, Dynamics 365 Vendors use a party-entity model with separate Address and Contact records. We map Info.Net vendor payment terms to Dynamics 365 Payment Terms, lead times to the Vendor lead time field, and primary contact to the Vendor Contact person record. Multi-contact handling differs between ERPs; we extract all contacts from Info.Net and create primary and secondary Contact records linked to the Vendor party in Dynamics 365. Vendors without a VAT or tax registration number are flagged for manual verification before production migration.

Info.Net supports custom fields on Items, Customers, and Vendors. We extract custom field definitions (name, data type, valid values for picklists) during discovery, pre-create equivalent custom fields in Dynamics 365, and map values during migration. Any custom fields with no matching target in the Dynamics 365 data model are flagged in the discovery report with a recommendation (create custom field, map to an existing unused standard field, or archive as a reference document). Custom field migration is a prerequisite phase before any standard object import so that dependencies are satisfied.

Info.Net User accounts carry role assignments and permission sets. We map Info.Net roles to equivalent Dynamics 365 security roles (Business Central Essentials, Premium, or Finance/SCM role-based security groups). We cannot preserve individual password hashes; users receive password reset instructions after migration. Active and inactive user status is preserved: inactive Info.Net users become inactive Dynamics 365 users pending admin reactivation. User contact information and email addresses migrate to the Azure Active Directory-linked user record.

Info.Net inventory locations and bins map to Dynamics 365 Warehouse and Location records. If Info.Net uses multi-bin or multi-shelf location tracking, we create corresponding Location hierarchies under the parent Warehouse. Location capacity data (if defined in Info.Net) migrates to the Warehouse location capacity fields. Inventory transactions reference the correct Location in Dynamics 365 via the warehouse mapping built during discovery.

Open and history Purchase Orders from Info.Net migrate to Dynamics 365 Purchase Orders. Open orders are imported as Pending Receipt status; completed orders migrate as history with their current status. Line items resolve the Vendor (via the vendor mapping) and Item (via the item mapping) references. Scheduled delivery dates and quantities preserve from Info.Net. Orders with no matching Vendor in Dynamics 365 are held in a vendor reconciliation queue.