Cross-Platform Contact ID Cloning — 4 Intelligent Routing Paths
Advanced cross-platform pipeline synchronization between Follow-Up Boss and GoHighLevel. The core innovation: cross-platform ID cloning — storing each platform's contact ID as a custom field in the other, enabling instant lookups on subsequent syncs. 4 intelligent routing paths handle every possible contact data scenario. Production-deployed with zero testing margin — once live, no testing allowed.
// Cross-Platform ID Cloning
The fundamental architecture decision: store each CRM's contact identifier inside the other CRM as a custom field. FUB's "people ID" is stored as a custom field in HL. HL's "contact ID" is stored as a custom field in FUB. After the first sync, every subsequent lookup is instant — no searching by phone or email needed.
// FUB People ID in HL
FUB people ID stored as a HL custom contact field
Enables HL to look up the FUB person directly — no search needed
// HL Contact ID in FUB
HL contact ID stored as a FUB custom field
FUB can locate the HL contact instantly on pipeline stage change
Most efficient path (Route 1) is used for all contacts after first interaction
Reduces API calls, increases speed, eliminates search ambiguity
// 4 Intelligent Routing Paths
When a pipeline stage changes in FUB, the automation needs to find and update the corresponding HL contact. Not every contact has the same data available. 4 routing paths handle every scenario — from the most efficient direct update to fallback searches by phone, email, or both.
// Route 1 — Direct Update (Most Efficient)
Contact has HL contact ID stored + has email or phone
Direct update — skips all search logic, updates stage immediately
This is the path for all previously-synced contacts
// Route 2 — Phone Search
No HL contact ID stored, no email, but has phone number
Search HL by phone number, find contact, update stage
After update — clones the contact ID for future Route 1 access
// Route 3 — Email Search
No HL contact ID stored, no phone, but has email
Search HL by email, find contact, update stage
// Route 4 — Dual Search
No HL contact ID stored, but has both email and phone
Search by either identifier, find contact, update stage
Widest search net — maximum chance of finding the HL contact
// HL Workflow Auto-Trigger
// Stage Change to Pipeline
All 4 routes update a custom field in HL with the new stage value
HL VA built a workflow: when custom field updates, auto-move opportunity pipeline stage
End result: FUB agent changes stage in FUB, HL pipeline auto-updates
// Production Constraints
Once 100% deployed — no testing allowed on live system
Zero-downtime deployment — had to get it right before going live
"Pretty large modules/workflow" — complex routing logic with no room for error
// Build Scale
4 routing paths with full conditional logic
Cross-platform ID cloning for long-term efficiency
HL workflow auto-triggers on custom field update — fully automated chain
