Operational migration
Populate a Stoneware company through controlled, idempotent migration workflows without creating duplicate business engines.
Exact buttons and available actions can vary with company plan, role permissions and enabled capabilities. Stoneware workflow rules and server-side checks remain authoritative.
Purpose
The StonewareMigration companion workspace is company-admin-only and exists to orchestrate real Stoneware/CRM/quote/invoice/procurement workflows during migration or demo preparation.
Canonical engines
CRM records remain CRM-owned, quotes are created through the Stoneware commercial controller, accepted quote lifecycle uses canonical reservation/allocation/fulfilment services, invoices/payments remain core-owned, and procurement uses canonical purchase-order/shipment services.
Idempotency
The companion maintains an idempotency ledger so re-running a migration does not blindly duplicate companion-created records.
Typical coordinated pack
The v2.9.5 production pack supports connected sample/migration flows spanning Accounts, Contacts, Leads, Opportunities, Activities, Quotes, accepted quote fulfilment, invoices/payments, purchase orders and inbound shipment/container flows.
Before production use
Validate mappings and company boundaries on staging, reconcile counts/totals, review failed rows, and keep the source export as evidence before wider production import.