Migrate from Rootstock Cloud ERP to Microsoft Dynamics 365 Business Central

Rootstock Item records map to D365 Released Products with Item number, name, unit of measure, and costing method (standard/average) preserved. Stocking policies, lot size rules, and shelf-life parameters require type mapping to D365's coverage and storage dimensions. We extract Item-specific custom fields from Salesforce and map them to D365 product attributes or extension fields.

Rootstock GL accounts map to D365 Main Accounts with account type, postings, and intercompany settings. Rootstock segment-based accounts (if configured) map to D365 Financial Dimensions with the segment values established as dimension values before any transactional data loads. Multi-company configurations require each company (legal entity) to have its own chart of accounts created in D365 first.

Rootstock Account records (the Salesforce Account object with customer-specific fields) map to D365 Customers. Customer-specific fields on Rootstock—credit limits, payment terms, tax codes, W-9 status—map to D365 Customer fields or extension properties. We resolve address books for multi-country configurations and preserve currency and payment terms from Rootstock.

Rootstock Vendor records (Salesforce Account with Vendor checkbox) map to D365 Vendors. Vendor-specific fields including purchase terms, W-9/1099 settings, EDI identifiers, and multiple vendor sites map to D365 Vendor extension fields. We resolve the primary vendor address and establish any vendor-specific purchase charge account before PO migration.

Rootstock Sales Orders map to D365 Sales Orders with header fields (customer, ship-to, terms, warehouse) and line items referencing the Released Product. Open orders migrate with their fulfillment status preserved so partial shipments can be completed post-migration. We resolve the Customer account and the Sales Order header Warehouse before inserting lines.

Rootstock Purchase Orders map to D365 Purchase Orders with header and line structure. Receipt linkages and approval status require mapping to D365 workflow states. Vendor records must exist before PO import to satisfy the vendor account lookup, and any landed cost or charges configuration from Rootstock maps to D365 charges codes.

Rootstock Work Orders map to D365 Production Orders with routing steps, labor estimates, and material allocations. BOM references on Work Orders require the BOM revision to be migrated first. If Rootstock Work Orders are linked to Sales Orders, we preserve the link in a D365 extension field since D365 links production to sales through different mechanisms (Sales Order picking or project).

Rootstock BOMs with versioning and effective dates map to D365 BOM and BOM Version records. Multi-version BOMs in Rootstock require active-revision selection—we extract the version history, apply a selection rule to identify the current effective BOM for each Item, and preserve obsolete BOM references in a custom BOM Obsolete_Revision__c field. Alternate BOMs for manufacturing constraints map to D365 alternative BOM versions.

Rootstock inventory locations map to D365 Warehouses and Locations. Complex multi-site hierarchies (regions > plants > warehouses > bins) require pre-mapping in a location matrix before migration because D365 warehouse management uses location directives and license plate numbers that must be configured before inventory transactions load. We flag any circular location assignments from Rootstock for customer resolution.

Rootstock lot and serial traceability links Items to source documents and inventory transactions. We migrate lot master records and serial number assignments as inventory dimension groups in D365, with full traceability preserved through D365's inventory dimension tracking on-hand quantity and transaction records. Lot/serial on-hand quantities migrate as inventory transactions linked to the dimension.

Rootstock Purchase Receipts map to D365 Product Receipts linked to the corresponding Purchase Orders. Receipt dates and partial receipt flags are reconciled against destination inventory posting. We map Rootstock receipt quantities to D365 product receipt lines with the vendor invoice reference preserved where available.

Fixed asset records are available in Rootstock Advanced tier and map to D365 Fixed Assets. Depreciation schedules, depreciation methods, and accumulated depreciation balances require field-level mapping. We migrate asset masters with their depreciation configuration but recommend the customer's fixed asset accountant review depreciation calculations post-migration for accuracy against local tax regulations.

Rootstock Project records (if used for project-based manufacturing or job costing) map to D365 Projects with project headers and cost entries. Billable rate schedules and project billing rules may require reconfiguration in D365 Project Management and Accounting. We migrate project structure and cost history; billing configuration is scoped as post-migration setup.

Rootstock ECOs managing BOM and engineering change approvals map to D365 Engineering Change Orders with affected BOM revisions. Approval workflow history and electronic signatures from Rootstock do not migrate as active approval records; we migrate ECO headers and affected items and flag approval state for manual re-approval in D365. Engineering revision control requires D365 product revision setup.