Migrate from Infor SyteLine / Infor CloudSuite Industrial to Microsoft Dynamics 365 Business Central

SyteLine Customer master records map to D365 Customer, which covers both individuals and companies. Address records, payment terms, credit limits, and salesperson assignments transfer as Customer fields and related Address records. Customer types (prospect, competitor, house account) map to D365 Customer Templating or a Customer Group dimension. Multi-site customers require address-site linkage preserved via the Customer's Address records with the corresponding site identifier carried as a custom field.

SyteLine Vendor records map directly to D365 Vendor. Address, banking information, and purchasing terms transfer as Vendor fields and related Address records. Vendors must be imported before Purchase Orders to satisfy referential integrity in D365, matching the same sequencing constraint SyteLine enforces at import time. Vendor holds or blocking flags map to D365 Vendor blocking status.

SyteLine Items (stocked, non-stocked, service, and labor) map to D365 Item records with type mapping: stocked items to Item Type = Stocked Item, non-stocked to Item Type = Non-Stock, service to Service, and labor to Service. Cost layers (standard, average, FIFO) transfer as D365 Costing Version entries. The Item's product type group determines the D365 Item Category assignment, which controls posting setup and inventory valuation method.

SyteLine BOMs map to D365 BOM records. BOM versions with effective date ranges transfer as D365 BOM Version entries with active-from and active-to dates. Component lines map with quantity-per, scrap percentages, and operation numbers preserved. For D365 F&SCM, BOMs with production routing attach to Manufacturing routes; for Business Central, BOMs attach to the production BOM structure used by the Production Journal. Complex multi-level BOMs require flattening or hierarchical preservation depending on the customer's engineering requirements.

SyteLine Routing data maps to D365 Route records with operations, work centers, setup times, run times, and queue times preserved. Work center definitions (machine capacity, labor availability, costing rate) transfer to D365 Work Center or Machine Center records depending on the operation type. Route versions with effective dates map to D365 Route Version with the same validity window handling as BOM versions.

SyteLine Jobs are the core manufacturing work-order object and map to D365 Production Order. Job status (released, complete, closed) maps to Production Order Status. The Job's linked BOM and Routing references transfer as the Production Order's BOM Version and Route Version. Job material issues, labor postings, and operation completions map as inventory transactions against the Production Order. Open Jobs transfer as Firm Planned or Released Production Orders; completed Jobs transfer as Finished Production Orders with historical ledger entries.

SyteLine Sales Order header and line structure maps to D365 Sales Order. Customer references, order dates, due dates, and salesperson assignments transfer as header fields. Line items map with item number, quantity, unit of measure, unit price, line discounts, and tax area preserved. Order delivery schedules (the promise date lines) map to D365 Sales Line Delivery records. Blanket order releases map to D365 Blanket Sales Orders with release lines linked to the blanket.

SyteLine Purchase Order header and line structure maps to D365 Purchase Order. Vendor references, order dates, and payment terms transfer as header fields. Line items map with item number, quantity, unit of measure, cost price, and charges. Blanket PO releases map to D365 Blanket Purchase Orders with release lines. Vendor confirmations and expected receipts require separate mapping because SyteLine tracks confirmation status differently from D365's receipt registration workflow.

SyteLine GL Chart of Accounts with account codes, descriptions, account types, and posting definitions maps to D365 Chart of Accounts. Sub-account segments used for cost-center or department reporting transfer as D365 Dimensions with Main Account and Dimension Value assignments. Account validation rules (posting group restrictions, blocked accounts) map to D365 General Posting Setup and General Journal restrictions.

SyteLine multi-site configurations require a decision during scoping: D365 F&SCM maps each SyteLine site to a separate D365 Warehouse/Location with independent inventory, production, and purchasing parameters. D365 Business Central maps sites to Locations within a single Company or to separate Companies for full financial isolation. Site-specific item data (site-level cost, on-hand quantity) transfers as inventory ledger entries against the target Location. Inter-site transfer orders map to D365 Transfer Orders.

SyteLine Projects wrapping job costing, billing, and revenue recognition map to D365 Project records. Project header data transfers with project type (Time and Material vs Fixed Price) mapped accordingly. Cost entries (labor, materials, expenses) map as D365 Project Journal lines. Billing records map to D365 Project Invoice lines. ETO projects with engineering change orders require a separate review to determine whether change orders map as project amendments or separate project phases.

SyteLine Quotes (generated via CPQ or manual entry) map to D365 Sales Quote. Quote headers and configuration lines transfer with customer references, item configuration, pricing, and expiry dates preserved. For SyteLine CPQ-driven configuration data, the configuration parameters map as Sales Quote line item attributes or as a linked configuration document depending on the destination D365 edition. Expiry status and reason codes transfer as Quote status flags.

Open payables and receivables transfer as D365 open ledger entries with customer/vendor links, amounts, due dates, and payment terms. Invoice and credit memo status flags (open, paid, partial, disputed) map to D365 Document Status. For AP, vendor invoice numbers and invoice dates preserve for reconciliation. For AR, payment terms, due dates, and aging buckets transfer. Closed AP/AR records typically remain in the source system for historical reporting; only open balances migrate to avoid re-creating closed records.

SyteLine custom fields stored as extended SQL columns map to D365 extension fields (AL in Business Central, X++ extensions in F&SCM). We inspect the full SyteLine column set during extraction to identify user-defined fields not present in the standard SyteLine data dictionary. Unsupported SyteLine enumerated list types map via value-mapping tables to D365 option set or enum fields. Custom field naming conventions are preserved with a sl_ prefix to distinguish migrated SyteLine fields from natively created D365 fields.

SyteLine Employee records map to D365 Human Resources Worker (in F&SCM HCM) or Employee (in Business Central). Name, department, job title, employment status, and compensation data transfer as Worker or Employee fields. If the HR module is not active in SyteLine, employee data may be partial; we flag incomplete records for customer review. Production worker rates used in Job costing transfer as D365 Resource or Work Center cost rates depending on whether the worker is machine or labor-based.

SyteLine file attachments stored at the database or file-system level cannot be extracted via the standard migration utility. Blobs attached to transactional records require manual export from the SyteLine file repository before migration, which is handled as a separate step outside the standard migration scope. We recommend the customer export attachments to a shared file store (SharePoint, Azure Blob) and link them via D365 document handling post-migration.