Migrate from SYSPRO to Microsoft Dynamics 365 Business Central

SYSPRO Customer master records map to D365 CustCustomerV3 (F&O) or Customer (Business Central). We extract full address structures, contact information, payment terms, and any custom Form Entry fields attached to the customer take-on program. Multi-site customers require us to determine whether the SYSPRO customer is shared across sites (maps to one D365 customer with addresses) or site-local (maps to separate D365 customers with cross-reference fields). SYSPRO credit limit and hold status map to D365 Customer credit limit and responsible party fields.

SYSPRO Supplier master records map to D365 VendVendorV3 (F&O) or Vendor (Business Central). EDI and XML trading-partner flags from SYSPRO do not have a direct D365 equivalent; we document these flags in the inventory deliverable and the customer's implementation team configures EDI via D365 Data Management Framework or a third-party connector post-migration. Contract pricing and landed cost codes migrate as vendor trade agreements in D365.

SYSPRO Inventory items carry extensive product attributes: unit of measure conversions, stocking locations, cost layers (FIFO, Standard, Average), and warehouse-specific quantities. Multi-warehouse setups require us to flatten or pivot bin-level data into D365 warehouse and location structures. SYSPRO stocking UOM conversions map to D365 unit of measure groups. Costing version data migrates to D365 costing configuration. We flag any SYSPRO items with negative on-hand or inconsistent cost layers for customer review before final load.

Open and historical sales orders migrate with header fields (customer account, order date, terms, delivery address) and line items (item number, quantity, unit price, line discount, tax). SYSPRO back-ordered lines that remain unfulfilled are flagged separately; the customer decides whether to carry them as open orders in D365 or archive them. Fulfillment status from SYSPRO maps to D365 line status. Sales agreement and blanket order flags migrate to D365 sales agreements.

Purchase order headers and lines migrate including receipt status and expected delivery dates. Blanket PO releases and EDI/XML export flags are preserved to maintain supplier relationship continuity. SYSPRO multi-site POs require us to split header and lines by site before mapping to D365 purchasing entities. Receipt status flags determine whether lines migrate as confirmed, received-in-full, or invoiced-matched in D365.

SYSPRO BOM structures with multi-level component routing and phantom assemblies require recursive extraction before we can flatten them for D365. We preserve bill versions and effective dates per SYSPRO BOM revision, then map to D365 BOM versions with from-date and to-date validity. Phantom assemblies in SYSPRO become D365 phantom BOM lines. Route versions (work centers, operations, setup and run times) migrate as D365 production route configurations. BOM quantity per assembly and scrap factors are mapped to D365 BOM line quantity and scrap percentage.

SYSPRO Jobs are the manufacturing work-order entity tied to routing, labor posting, and material issues. Job status, work-center assignments, and WIP valuations migrate to D365 Production orders (F&O) or Manufacturing work orders (Business Central). Open jobs with material issues and labor postings become D365 production orders with lines and route operations. Closed jobs migrate as production order history. WIP balances are reconciled to D365 WIP inventory postings.

AR and AP invoices including multi-currency headers and line-level tax codes migrate. SYSPRO contra-invoice relationships used for AP netting are preserved via custom mapping logic with offset accounts. Historical posted invoices migrate to D365 as invoice journals rather than open receivables or payables; open invoices migrate as open AR/AP transactions. Credit notes migrate with their reference original invoice for traceability.

SYSPRO account codes, cost-center structure, and journal-entry templates extract from the master file setup. We map account types and posting groups to D365 main account type, posting type, and financial dimension framework. SYSPRO cost centers become D365 financial dimensions with dimension values migrated as dimension value records. Account validations and posting definitions require configuration in D365 by the customer's finance team.

SYSPRO custom Form Entry fields attach to specific programs (Customer take-on, Order entry, etc.) and can reference lookup tables or carry formula-driven values. We extract both the field definitions (table and column names, data type, lookup relationship) and the field data separately. The lookup table data migrates first; the form field data follows with the parent entity. Formula fields may require re-evaluation in D365 because the underlying calculation context changes. Custom fields in D365 F&O are implemented via extensions; Business Central uses AL-based custom fields.

SYSPRO multi-site architecture with independent module sets and shared or site-local master data requires us to map each SYSPRO site to a D365 legal entity or site/warehouse combination. We identify which records are site-local versus shared and ensure cross-site transactions are not split during extraction. Shared master data (global customers, global vendors) migrates once to the D365 legal entity that owns the master data; site-local records migrate to their corresponding D365 entity. This prevents orphaned transactions and duplicate master records.

SYSPRO operators carry security-role assignments and MFA enrollment records. Operator-level restrictions must be translated to the D365 security role model, which uses a different role concept. We extract operator definitions including program access rights, site restrictions, and warehouse authorizations, then map them to D365 security roles and duties during the D365 configuration phase. Active operators without matching D365 users go to a reconciliation queue for the customer to provision before production migration.

SYSPRO stocking locations and bin structures map to D365 warehouse and location records. Multi-bin setups require location dimension configuration in D365. SYSPRO warehouse transfer orders between sites map to D365 inter-company transfer orders or stock transfer journals depending on whether the sites share a legal entity. Bin-level on-hand quantities are reconciled against the inventory master after migration.

SYSPRO tax codes and tax group assignments at the customer, vendor, and item level migrate to D365 sales tax groups and item tax groups. SYSPRO multi-jurisdiction tax configurations require mapping to D365 tax authority and tax settlement period definitions. We flag any SYSPRO tax codes that do not have a direct D365 equivalent for the customer's tax consultant to resolve before go-live.