Auditing Custom Integrations Before CRM Migration
Undocumented Zapier Zaps, contractor webhooks, and ownerless scripts are the silent killer of CRM migrations. Teams discover 20+ shadow connections only after cutover, when workflows are already broken.
We run the full integration audit before any data moves.
Sound Familiar?
These are the exact gaps that surface when a CRM migration starts without an API audit:
- The migration plan lists eight "known" CRM connections, while API logs show twice that many callers nobody remembers
- A former contractor's Google Apps Script still posts won deals into a spreadsheet that finance silently depends on
- Zapier and Make workspaces hold Zaps owned by leavers, with no documentation of what breaks if the old CRM dies
- Webhook endpoints live on a server that will be decommissioned with the old CRM, and nobody mapped the dependents
- Cutover is booked, dual licences are burning cash, and the integration inventory is still a slide titled "TBC"
Companies migrating off Salesforce, Dynamics, or legacy CRMs routinely discover 20+ undocumented connections only after cutover. One recruitment agency estimated "maybe 10 or 12" automations and an audit found 47. The ones missed after go-live dropped follow-ups on active deals. Hunt them before data moves.
What a Pre-Migration Integration Audit Actually Does
API logs → Zapier discovery → webhook map → scored inventory. No guessing what former employees left behind.
Capture API Traffic
Review inbound and outbound CRM API calls over a representative window
Hunt Shadow Automations
Inventory Zapier, Make, Apps Script, and contractor jobs with owners and triggers
Map Webhooks
Trace every endpoint, secret, and dependent system that will die with the old CRM
Score and Handover
Prioritised audit report so migration starts with a complete map, not tribal knowledge
Everything You Need for Migration Discovery
API Call Inventory
Inbound and outbound API traffic against the CRM is logged over a representative window so every caller, volume, and field touch surfaces.
Zapier and Make Discovery
Every Zap, scenario, and folder is listed with owner, trigger, and blast radius, including Zaps built by people who left years ago.
Webhook and Endpoint Map
Webhook URLs, signing secrets, and scheduled jobs are traced to the systems that depend on them before the old CRM is switched off.
Ownerless Script Hunt
Google Apps Scripts, Power Automate flows, custom middleware, and contractor-built jobs are found via credentials, DNS, and team interviews.
Dependency Risk Score
Each connection is scored for revenue impact, data sensitivity, and rebuild effort so the migration plan attacks the silent killers first.
Pre-Move Audit Report
A board-ready inventory with owners, volumes, and rebuild recommendations, delivered before any data leaves the source CRM.
Platforms and Tools We Audit Across
From 8 "Known" Connections to 27 Mapped Before Cutover
How a Johannesburg manufacturer migrating off Salesforce avoided day-one outages by auditing custom integrations first.
The Incomplete Inventory
- Migration slide listed eight native connectors: email, Xero, support, and marketing
- Nobody owned the Zapier workspace built by a contractor who left in 2022
- API logs showed callers the settings page never listed
- Cutover was six weeks out with dual Salesforce licences already burning
- IT assumed "if it is not in Setup, it does not exist"
The Full Audit Map
- Two-week audit found 27 live connections, including 11 Zapier Zaps and 3 ownerless scripts
- A quality webhook on retired contractor infrastructure was flagged before cutover
- Each connection scored for revenue impact and rebuild effort
- Reconnection work started against a complete list, not tribal knowledge
- Go-live weekend: zero day-one workflow outages
Before vs After a Custom Integration Audit
How It Works
From first conversation to a board-ready integration map in one to three weeks.
Share Your Stack
Current CRM, known connectors, Zapier or Make access, and why you are migrating. We start hunting what the slide deck missed.
Free Scoping Call
30-minute call to size the audit, agree on API log windows, and set which revenue paths must be proven before data moves.
Run the Integration Audit
We inventory APIs, Zaps, webhooks, and ownerless scripts, then score each connection for blast radius and rebuild effort.
Hand Over the Map
You receive a prioritised inventory and rebuild plan so migration and reconnection work against known ground, not tribal knowledge.
Frequently Asked Questions
Why do undocumented custom integrations break CRM migrations?
Most migration plans only list the connectors on the CRM settings page. The silent killers are Zapier Zaps, Google Apps Scripts, contractor webhooks, and legacy API jobs that never made the inventory. DataSovren case studies show migrations that documented fourteen known integrations still failing when an undocumented webhook, built years earlier by a departed consultant, depended on the old CRM's infrastructure. Engaging Partners and HubSpot both flag the same pattern: workflows stop after cutover because the ecosystem was never fully mapped.
How many shadow integrations should a mid-market company expect?
Productiv's State of SaaS Report (via AMW 2026) puts mid-market companies at about 129 SaaS apps on average. Workato's Automation Index finds 67% of mid-market and enterprise firms use at least one iPaaS tool (Zapier, Make, Workato, and similar), with about 40 automated workflows in active use. A 2024 B2B SaaS integrations survey found businesses averaging 29 integrations overall. Practitioner audits regularly surface 20 or more undocumented connections once API logs, Zapier workspaces, and ownerless scripts are included, far above the "eight we know about" on the migration slide.
What does discovering broken workflows after cutover actually cost?
DataSovren reports one manufacturer spending $60,000 (about R990,000 at R16.54 to the dollar) on emergency consulting plus $23,000 (about R380,000) in margin loss after an undocumented webhook broke at go-live. Rebuilding a single integration after the fact typically costs $2,000 to $8,000 (about R33,000 to R132,000), and complex ERP links can exceed $15,000 (about R248,000). Productiv estimates mid-market firms already burn $200,000 to $500,000 a year (about R3.3 million to R8.3 million) on hidden integration maintenance before a migration ever starts.
How long does a full custom integration audit take?
DataSovren recommends a complete data and integration inventory of one to two weeks covering every field, integration, webhook, and scheduled job. Practitioner migration write-ups report that a focused automation audit often takes two to three days and saves two to three weeks of post-migration firefighting. Our full audits, including API log review, Zapier/Make discovery, webhook mapping, and stakeholder interviews, typically land in one to three weeks depending on how many workspaces and legacy scripts exist.
How is an integration audit different from reconnection or migration planning?
The audit is the discovery step that happens before any data moves. It answers "what is actually connected to this CRM?" Migration planning covers stakeholders, data cleanup, dual-run, and rollback. Integration reconnection rebuilds known connectors against the new CRM at cutover. Skipping the audit means planning and reconnection work against an incomplete map, which is how day-one outages happen.
How much does a CRM custom integration audit cost?
Focused mid-market audits typically land between R25,000 and R80,000 depending on CRM age, Zapier/Make sprawl, and how many custom scripts need tracing. Against R990,000-class emergency consulting, R33,000 to R132,000 per surprise rebuild, and R3.3 million to R8.3 million a year in hidden maintenance, most clients recover the audit cost inside the first dual-licence month they do not waste fixing unknowns.
Audit Custom Integrations Before You Migrate
If your CRM migration plan only lists the connectors on the settings page, you are planning against tribal knowledge. The Zapier Zap nobody owns is the one that breaks Monday morning.
Tell us which CRM you are leaving, which you are moving to, and how much of the stack you already know about. We will show you how a full integration audit fits before any data moves.