Rescue · Salesforce → HubSpot
Your Salesforce to HubSpot migration did not finish. We can.
Partly migrated, partly not, and no reliable account of which is which.
We establish what actually transferred, what did not, and what is still recoverable from the source — then quote a fixed recovery scope against that evidence rather than against a guess.
- Source left intact
- Recoverability established first
- Fixed recovery scope
- Verification report
Price cue, ex GST
Assessment from $750
Check what is recoverable Or call 1300 652 280A written finding on what transferred, what is missing, what is recoverable and what it will take. Yours to keep, whether or not you engage us for the recovery.
- Australian managed
- Delivered remotely
- Source data never deleted
- Verification report at sign-off
What goes wrong on this route
Custom objects had no HubSpot equivalent and the data was quietly dropped
Opportunity stage history did not migrate, so forecasting has no baseline
Record ownership defaulted to one user, and pipeline reporting is meaningless
Activity history came across without its association to deals
Salesforce formula and roll-up fields arrived as empty properties
Duplicate contacts multiplied because the matching key was the wrong field
Why retrying the tool usually makes it worse
A failed migration is a diagnostic problem before it is a technical one. The tool reports success on items it delivered incorrectly, which is why the same run repeated produces the same silent failures plus a fresh set of duplicates.
- Nothing is re-run until we know why the first attempt failed. A cause that is not addressed simply reproduces itself.
- The Salesforce source is preserved and never deleted as part of a recovery. Decommissioning is your decision, made later and separately.
- Where the destination already holds partially migrated data, we reconcile before adding to it, so recovery does not create duplicates.
- Mapping decisions are agreed with you in writing before any transfer runs.
- Anything genuinely unrecoverable is documented as unrecoverable. We do not quietly leave it off the list.
The proof you keep
You will know exactly what came back, item class by item class.
A recovery ends the way a migration does: source totals set against recovered totals, every exception itemised and owned. The figures below are an example of the format, not a specific client.
Recovery Verification Report
Salesforce → HubSpot recovery · Example format
| CRM object | In source | Recovered | Status |
|---|---|---|---|
| Contacts | 148,206 | 148,206 | Verified |
| Accounts → companies | 19,884 | 19,884 | Verified |
| Opportunities → deals | 12,441 | 12,441 | Verified |
| Activities & notes | 1,088,220 | 1,087,946 | 274 Accepted Exception |
| Attachments | 62,118 | 62,118 | Verified |
| Custom fields mapped | 128 | 128 | Verified |
Accepted exceptions are itemised individually with a reason, never summarised as a total. Anything genuinely unrecoverable is recorded as unrecoverable.
Free · About three minutes · No sales call required
Tell us what happened. We will tell you what is recoverable.
The route is already filled in. Four steps, and an engineer reviews every answer — a failed migration never receives an automated number, it receives an assessment.
Questions we get on this route
What is the biggest risk moving off Salesforce?
Custom objects. Salesforce lets you build data structures HubSpot has no equivalent for, and the honest answer is sometimes that a custom object has to become a HubSpot custom object, sometimes a property set, and sometimes an archive. Deciding that per object before import is the difference between a migration and a loss.
Does opportunity and pipeline history survive?
Deal records and their current stage migrate reliably. Stage transition history is achievable but route-specific and needs to be scoped deliberately, because it is what your forecasting baseline rests on. If it cannot come across in full, you are told before the import rather than after.
Can you just re-run the migration?
Not as a first step. Running a tool again over a partially migrated destination turns one problem into two: items that arrived correctly get duplicated, and items that failed silently fail again for the same unaddressed reason. We diagnose the cause first, then choose between a targeted top-up, a clean re-run into a staged target, or a manual extraction.
Is the data still recoverable?
Usually, provided the source has not been deleted, downgraded or decommissioned. Most platforms hold data for a defined period after a licence is removed, but that window is finite and it starts without telling you. Establishing what the source still holds is the first thing the assessment does, because everything else depends on the answer.
What does the assessment cost?
From $750 ex GST. Where we go on to perform the recovery, the assessment fee is credited against the recovery quote. If you take the findings to another provider or handle it internally, the document is still yours to keep.
Do you work on migrations someone else performed?
Most of our rescue work is on migrations performed by an internal team or another provider. We are not interested in apportioning blame. The assessment states what happened technically, which is generally more useful to everyone involved than a narrative about who was at fault.