Solution challenges
Solution challengeDelivered
Salesforce to HubSpot migration where marketing already uses HubSpot
The portal already exists, so the migration is a merge rather than a clean build.
Project-level detail for this record is still being verified internally. Treat the summary below as capability and approach, not as a specific delivered claim.
- Forbidden's experience
- Forbidden approaches this as a consolidation problem: an existing marketing portal already holds contacts, activity and automation that must survive the arrival of the Salesforce commercial model.
- Architecture considerations
- Existing HubSpot contact records versus incoming Salesforce accounts and contacts
- Deduplication and matching rules agreed before any load
- Lifecycle stage model reconciled across marketing and sales definitions
- Sync history and legacy Salesforce-HubSpot integration data
- Ownership and permissions once sales joins the portal
- Common failure points
- Loading Salesforce data on top of marketing data without a matching strategy
- Keeping both lifecycle models and reconciling neither
- Leaving the old sync running during cutover
- Rebuilding Salesforce automation literally instead of redesigning it
- Worth resolving in discovery
- How long has the marketing portal been running, and how clean is it?
- Is the existing Salesforce-HubSpot sync bi-directional?
- Which system currently owns lifecycle stage?
- What has to be reportable on day one after cutover?