Leaving it, or living with it.
Most of our Salesforce work starts the same way — an org four admins configured across six years, reporting nobody trusts, and a renewal quote that finally forced the question. We do both halves: moving off it with the history intact, and making it behave when it stays.
The org is not the problem. The decisions inside it are.
Record types nobody can explain, validation rules that fire on the wrong profile, three fields that all mean customer. Moving or staying, the work is the same — decide what each object means, then make one system say it.
Twenty years of history.
SalesforceWhat people call us about.
Migration off, with the audit trail
Objects, record types, activity history, automation and reporting moved to HubSpot without re-keying, and without losing the trail an auditor or a board would ask for.
Integration where it stays
Salesforce joined to billing, the product, the warehouse and the tools the rest of the company runs on, through private apps and serverless rather than a brittle point-to-point sync.
Org cleanup
Objects, fields, profiles and automation inventoried, every contradiction listed, and a data model rewritten to match how the business actually sells.
Pardot and Marketo, separately
Nurture, scoring and asset history are their own migration. We rebuild them against the new model rather than exporting them into a CSV nobody opens again.
Reporting that survives a board meeting
One definition of pipeline, bookings and churn, built from primary records and reconciled against billing rather than assembled in a spreadsheet the night before.
Audit, decide, move, hand over.
Audit
Objects, fields, record types, profiles, automation and integrations inventoried, with everything that contradicts something else written down.
Decide
What a customer is, which history is worth carrying, and who signs off on the number afterwards — agreed before anything moves.
Move
Migration or rebuild, run in stages against a sandbox and reconciled record by record before anyone switches.
Hand over
Admin training, documentation, and a support window with a named engineer.
The export is the easy part.
Anyone can move records. What sinks a migration is the reporting definition nobody agreed on, the automation that fires twice, and six years of activity history that turns out to matter to legal. Those get decided first or they get discovered late.
