Every replatform estimate in this category is really an integration estimate wearing a platform's name. We would rather tell you which of your systems will take longest before you sign anything than discover it in month three.
Pre-built endpoints for SAP, NetSuite, Salesforce, HubSpot and Microsoft Dynamics.
Each has its own page listing which records are shared, which way data flows, and when it syncs. Systems outside this list are integrated through the same documented API surface.
Material master, pricing conditions, stock and available-to-promise (ATP) dates, sales orders. ECC and S/4HANA.
ERP
Items, price levels, inventory by location, sales orders. Connects through NetSuite's standard web API (SuiteTalk REST).
ERP
Business Central and Finance & Supply Chain. Items, price agreements, inventory, orders.
ERP
Contacts, companies, deals, line items and behavioural events. We run this one ourselves.
CRM
Leads, accounts, opportunities with line items, price books. Works with Salesforce CPQ (configure, price, quote) if you use it.
CRM
The same documented API the storefront uses. Nothing is a privileged special case, so a bespoke integration is ordinary work rather than a platform exception.
API
Which system owns which field. Where two systems both believe they own price, someone has to decide, and it is much cheaper to decide in scoping than in production.
What your instance has been customised to do. Almost every ERP in this market carries a decade of business rules encoded in customisations, and the ones that matter are usually undocumented. Finding them early is the difference between a timeline and an apology.
What happens when a system is unavailable. How the site behaves when a connected system is down is decided at design time. A page that silently drops a stock row teaches buyers something worse than a page that says the feed is late.
Present, Partial or Missing, each rating followed by the specific observation behind it. Five business days, and there is no call first.