Migrate your Rootstock Cloud ERP data

Item master records are the foundation of Rootstock inventory, BOMs, and procurement. We migrate Items with all standard attributes including stocking policies, costing methods (standard/average), lot/serial control settings, and unit of measure conversions. Custom fields on the Item object carry over via Salesforce field mapping.

Sales orders include header fields (customer, ship-to, terms) and line items tied to the Item master. We migrate open and historical sales orders, preserving fulfillment status so partial shipments are not duplicated. We map Salesforce Account/Contact links to the order header.

Purchase orders manage direct and indirect materials procurement. We preserve PO headers, line items, receipt linkages, and approval status. Vendor records must exist or be migrated first to maintain referential integrity on the Vendor field.

Work orders represent manufacturing operations tied to a Sales Order or standalone job. We migrate work order headers with routing steps, labor estimates, and material allocations. BOM references on work orders are preserved through BOM ID mapping.

BOMs define multi-level component structures with quantities and operations. We handle single and multi-level BOM hierarchies, preserving engineering change control (ECO) status and effective dates. Phantom BOMs and BOM versioning are supported through direct field mapping.

Locations represent warehouses, plants, and stock points. We migrate location masters with address data, location types, and ABC analysis codes. Current on-hand quantities are migrated as separate inventory balance records linked to Item and Location.

Purchase receipts link to POs and update inventory. We migrate receipt records with their PO links and quantity information, but receipt dates and partial receipt flags must be reconciled against destination system expectations for receipt-date vs invoice-date accounting.

Rootstock maintains a full chart of accounts structure on Salesforce. We migrate GL accounts with their segment definitions, account types, and intercompany settings. Multi-company and multi-country chart structures are supported but require careful mapping to destination account numbering conventions.

Rootstock shares the Salesforce Account object for customer records. We migrate Accounts with standard fields plus any custom customer-specific fields. Credit limits, payment terms, and tax codes on the Account are preserved as Salesforce fields.

Vendor records are stored as Account objects with a Vendor checkbox in Rootstock. We migrate Vendor Accounts with associated purchase terms, W-9/1099 settings, and EDI identifiers. Multiple vendor sites per vendor are supported via the Account location model.

Lot/serial traceability links Items to source documents and inventory transactions. We migrate lot master records and serial number assignments with their associated transaction history. Full traceability chains (source PO to receipt to work order to shipment) are preserved where the source data contains complete linkage.

ECOs manage BOM and engineering change approvals. We migrate ECO headers and affected BOM revisions, but approval workflow history and electronic signatures must be evaluated per destination—some target systems do not replicate approval chain state.

Fixed asset records are available in Rootstock Advanced tier. We migrate asset masters with depreciation schedules, but depreciation method mappings and accumulated depreciation balances require field-level alignment with the destination's depreciation engine.

Project records in Rootstock collect costs across inventory, labor, and purchasing. We migrate project headers and cost entries, but billable rate schedules and project billing rules may need reconfiguration in the destination.

EDI integration settings define document types and partner mappings. We migrate EDI partner configurations where they exist as structured data, but translation maps and communication protocols are typically destination-specific and require re-implementation.