Prerequisites
You need admin access to your Zapier or LeadsBridge account, credentials for the systems on each side of your flows (ad platforms, CRM, email tools), and a Datahash Signals account. Do not switch anything off yet; the migration runs both systems in parallel until you have verified parity.
Step 1: Inventory your existing flows
Export or list every active zap or bridge. For each one, record the trigger, the destination, any field mappings or filters, and roughly how many records it moves per week. Flag the ones that touch revenue, such as lead sync to CRM and conversions back to ad platforms; these get verified most carefully.
Step 2: Rebuild the flows as Signals connections
Recreate each flow from the connector catalog. Typical replacements: Meta Lead Ads to Salesforce or HubSpot becomes a source-to-CRM connection; CRM stage changes to Meta or Google become CAPI and Enhanced Conversions destinations. Field mappings that lived inside individual zaps become mappings on the connection, with normalization and SHA-256 hashing of personal fields applied by default.
Step 3: Run in parallel
Enable the Signals connections while the old flows keep running. For lead delivery flows, dedupe on lead ID in your CRM so parallel running does not create duplicates, or route Signals to a staging list for the comparison window.
Step 4: Compare and cut over
After a representative window (one week covers most volume patterns), compare record counts and spot-check field accuracy between the two paths. When they match, pause the zaps or bridges one flow at a time, revenue flows last.
Step 5: Decommission
Once everything is cut over and stable, archive the old flows and revoke the credentials they held. Fewer standing credentials is one of the quiet wins of the migration.
Verify
Confirm every inventoried flow has a live Signals equivalent, weekly volumes match your baseline, and conversion events show healthy match quality in Meta Events Manager and Google Ads diagnostics. Check that no zap has fired since cutover.
Troubleshooting
If counts differ in parallel running, check filters first; zaps often carried undocumented conditions that need recreating on the connection. If a niche tool has no catalog connector, use the Signals webhook source as the bridge and tell us, because connector requests drive the roadmap. If duplicate leads appear during parallel running, tighten the CRM dedupe rule rather than shortening the comparison window.