Know before you move.
Portablov makes enterprise software portable. A free assessment of your estate answers three questions before you commit: can we move, what should move, and what should change.
Read-only — Portablov writes nothing to either platform. Migrating afterwards is optional.
Migration readiness
80%
Found in this estate
1,933 licences needed, not 2,840
$824,940 a year avoided against a seat-for-seat move.
42 of 144 fields will not arrive
28 have no destination equivalent; 14 are recommended to leave behind.
5 of 9 automations have no equivalent
Each is rebuilt, replaced or retired.
26 failures, 13 warnings
Across 4,327,906 records — each drillable to the exact field or person.
Every figure on this page is computed live by the Portablov engine from a synthetic demo estate.
Licences · What should move
You are about to buy 2,840 licences. You need 1,933.
528 accounts are deactivated, dormant, or hold a licence type with no destination equivalent — $824,940 a year that never needed buying. Every exclusion shows its evidence.
Explainable, never silent
Each user arrives with the signals behind the recommendation — last login, records owned, permission sets, licence type.
Priced per person, before you commit
$1,835,880 a year for the recommended selection against $2,660,820 for everyone. Override in bulk; every override is audited.
Orphaned ownership caught early
188,084 records are owned by people who are not migrating. The destination requires an owner — those records would be rejected on load.
Migrate
1,933
Review
379
Exclude
528
- EKEvelyn KimActive — 22 logins in 90 daysMigrate
- YMYusuf MoreauSystem AdministratorReview
- NCNadia CostaDeactivated in SalesforceExclude
Data model · What should change
144 fields. 102 carry forward.
28 have no destination equivalent and 14 are recommended to leave behind. The rest cross as 53 automatic mappings, 41 named transformations and 6 that lose fidelity.
Usage is measured, not judged
27 fields are populated on fewer than half of records, and custom fields average 65.8% against 81.6% for standard ones. Portablov reports the fill rate; whether a field still earns its place is your call.
Seven states, not two
Automatic, manual, transformation required, lossy, conflict, unsupported, intentionally left behind. A tool that only says "mapped" is hiding something.
Lossy is called lossy
Salesforce has four opportunity types; HubSpot has two. Portablov will map them, and tell you your renewal-versus-expansion reporting stops working.
- Tasktasksautomatic
- Caseticketstransform
- Leadcontactstransform
- Contactcontactsautomatic
- OpportunityLineItemline_itemstransform
- Opportunitydealstransform
Blockers · Can we move
Drill from a percentage to a person.
26 failures and 13 warnings across 4,319,465 validated records. Each names the exact object, field, user or automation — and what to do about it.
Automations judged against the destination
5 of 9 have no destination equivalent. Portablov names what each one does, so you can decide: rebuild, replace, or retire.
Blast radius, not just severity
Every finding carries who and what it affects — 1,933 people would receive a HubSpot onboarding email the moment their seat is created, and HubSpot cannot suppress it.
Blockers cap the score
A readiness percentage that hides a blocker is a lie. If a blocker is open, Portablov says "not ready" regardless of the weighted average.
- blocker
1,933 people will receive a HubSpot onboarding email
notifications.onboarding
- high
148,209 values will be dropped
Account.RecordTypeId
- high
612,884 values will be dropped
Contact.DoNotCall
- high
989,400 values will be dropped
Case.CaseNumber
- high
850,884 values will be dropped
Case.ContactId
What you get
Decisions you need to make before migrating.
The assessment does not end in a percentage. It ends in the short list of business calls that are yours to make — each one counted, each one showing its evidence. This is the real list from the demo estate.
379 users require review
Who moves, and who does not?
Portablov could not decide these on evidence alone — they are dormant but privileged, hold unusual permissions, or own records that matter. Each one needs a human call before a seat is bought.
Evidence · 1,933 recommended to migrate and 528 not recommended, out of 2,840 discovered users.
28 fields have no destination equivalent
What do you accept losing?
These fields cannot be expressed in the destination at all. Either the data is archived before cutover, recreated as a custom property, or knowingly dropped.
Evidence · 144 source fields analysed; 78.5% have a usable destination target.
5 automations need redesign
Who rebuilds the logic?
Apex triggers, validation rules and process builders have no direct destination equivalent. Each has to be rebuilt as a workflow, moved to an external service, or retired.
Evidence · Reported by validation against the destination connector’s declared capabilities.
188,084 records require ownership reassignment
Who inherits this data?
These records are owned by people who are not migrating. The destination requires an owner, so without a reassignment rule they would be rejected on load.
Evidence · Owned by the 528 users Portablov does not recommend migrating.
6 fields map lossily
Which reporting are you willing to lose?
These fields will carry across, but with less precision than they have today — collapsed picklists, narrowed types, or dropped granularity. Reporting built on them changes.
Evidence · 41 fields need a named transformation; 6 of those lose information.
1 object has nowhere to go
What happens to these records?
The destination has no comparable object. The records stay behind, move to a custom object, or are exported to a warehouse before the source is switched off.
Evidence · 8,441 records sit in objects with no destination target.
48 mapping issues are unresolved
What still needs a decision?
Every issue Portablov raised that nobody has acknowledged, resolved or waived yet. Each one names the object, field or person responsible.
Evidence · 14,656,439 records, fields or people affected across 48 open issues.
How it works
Seven stages, ending in a report you keep.
Read-only throughout. The last stage is a conversation — not a button that migrates your company.
- 1
Connect / Upload
Read-only OAuth, or an export you upload. Nothing is written anywhere.
- 2
Discover
Schema, records, users, automations.
- 3
Assess users
Who actually needs to move — and why.
- 4
Map data
What is worth carrying forward, and what has nowhere to go.
- 5
Identify blockers
What would stop the migration, named and counted.
- 6
Readiness report
Your answer, with the evidence behind every line.
- 7
Get migration help
Optional. Portablov turns the report into a plan and executes it.
After the assessment
Ready to move?
Portablov can turn the assessment into a migration plan and execute it. That part is a conversation with people, not a button.
No obligation. Plenty of assessments end in a decision to stay — made with the numbers in front of you.
Resolve the open decisions
Each call recorded against the object, field or person it affects — including what you have decided not to bring.
Agree how the lossy conversions land
Every picklist collapse, type narrowing and ownership reassignment signed off before anything moves.
Plan the sequence and the comms
A dependency-ordered load, a rehearsed dry run, and a plan for the 1,933 people the destination will email.
Move with approvals at every step
Nothing consequential happens without a named person approving it, after seeing how many records and people it affects.
Coverage
One path today. Built for many.
One model of schema, records, users and automations underneath, so a new path is an integration rather than a rewrite. Salesforce → HubSpot is the only path available today.
Salesforce Sales Cloud
Source connector
- Read-only access to schema, records, users and automations
- Or upload an export, if you would rather not connect anything
HubSpot Sales Hub
Destination connector
- Every field checked for a usable target — or named as having none
- Seat cost modelled per person; platform limits reported as risks
Further paths are in development. Each has to clear the same bar: it must be able to tell you what it cannot carry across.
Security
Built for the systems you cannot afford to get wrong.
The full threat model — and an honest statement of the certifications Portablov does not yet hold — is on the security page.
Read the security overviewRead-only by default
Nothing is written to Salesforce or HubSpot at any point.
Credentials never in the browser
OAuth material lives in a managed secret store and is referenced, never returned.
Your data stays yours
Every record is scoped to your organisation and checked server-side on every request.
Everything is on the record
Every change, override and approval written to an append-only trail with actor and time.
Find out what you would actually be taking with you.
Connect read-only and get a defensible answer in an afternoon instead of a quarter.