Do I have to tell my partner before starting?
No. First secure a Super Admin of your own and ask in writing for access, keys, code and documentation. Announce it once you hold every piece.
Guide · Switching partners
How to switch HubSpot partners without losing integrations?
Before announcing the change, make sure you hold a Super Admin of your own, the API keys, the code of every integration and the documentation. Then, in the first month, inventory workflows, integrations and properties with their owner, turn on alerts for the sources that bring data daily and only then remove the previous partner's access. In Chile and Latin America, what is hardest to recover are integrations running on the provider's servers.
- 6 minute read
- Access and keys
- Inventory in 30 days
- Chile and Latin America
What to ask for before telling them
| What to ask for | Where you check it | If it is missing |
|---|---|---|
| A Super Admin from your company | Settings > Users & Teams | You depend on the partner even to grant permissions |
| Apps and who installed them | Settings > Integrations > Connected Apps | You do not know what breaks when access is removed |
| Tokens and API keys | Development, under private apps | Integrations in a third party's name |
| Code and servers | Outside HubSpot: repository and hosting | The critical parts must be rebuilt |
| Workflow documentation | Each workflow, with its description and owner | Nobody can explain what each one does |
What must you hold before announcing the change?
A Super Admin from your company, not from the partner. Only a Super Admin can make someone else one, and Partner Admins, the role many partners work with, cannot add or remove Super Admins. If today the only person with full access belongs to the provider, that is the first step.
Then: the API keys and credentials for every integration, the code and where it runs, the documentation, the list of workflows and apps, and the contracts for connected tools. Ask for it in writing and verify every piece before announcing the change.
Where do your integrations live and who owns the code?
HubSpot shows you part of it. Under Settings > Integrations > Connected Apps, every app appears with its install date, who installed it and its last activity. Private apps and their tokens are in the Development section, and only Super Admins manage them.
What you do not see is the code running outside HubSpot: a middleware, a server in the provider's cloud or a scheduled job. That code is your integration. If it is not in a repository and an account in your company's name, ask for it; if the provider does not hand it over, document what it does and rebuild only what is critical.
How do you remove the previous partner's access without breaking anything?
In order. First reassign the records their users own and review the workflows that assign them tasks or send emails in their name. Then rotate the private apps' tokens: HubSpot lets you expire the old one immediately or in 7 days, which gives you time to update each integration. Finally, deactivate the partner's users.
Also check under Settings > Privacy & Consent > Partner Data Access which information you share, and under Account Management > Audit Logs the activity of the last 30 days. Deactivating before removing lets you roll back if something fails.
What should happen in the first month with the new partner?
Week 1, access and keys. Week 2, an inventory of workflows, integrations, properties and reports with owner and purpose. Week 3, alerts on every source that brings data daily and a risk list. Week 4, a prioritized plan and the first review with your management.
Watch out for a HubSpot change: from October 26, 2026, existing accounts can no longer create legacy private apps. Current ones keep working, but new integrations use Service Keys or projects-based apps. In Chile and Latin America, a handover is a good moment to sort this out.
Step by step in HubSpot
The handover, step by step
Six steps that do not stop your operation.
- 01
Secure a Super Admin of your own
Before any conversation, someone from your company with full access in Settings > Users & Teams.
- 02
Ask for access, keys, code and documentation
In writing and with a deadline: credentials for every integration, repositories, servers, the list of workflows and apps, and tool contracts.
- 03
Inventory what exists
Connected apps, private apps, workflows, properties and reports, with owner, purpose and what happens if they are switched off.
- 04
Turn on alerts before touching anything
A notice for every source that brings records daily, so you know if something breaks during the change.
- 05
Rotate keys and remove access in order
Reassign records, rotate tokens with delayed expiry and deactivate the previous partner's users; remove them once everything works.
- 06
Leave the plan and documentation up to date
A prioritized backlog, a living inventory and a manual in your company's name, reviewed in the first meeting with your management.
What it looks like done right
What changes when the handover is orderly
- Your company has full control of the portal from day one.
- Every integration has code, keys and an owner in your name.
- If something breaks during the change, an alert warns you.
- The new partner starts from an inventory, not from assumptions.
Common mistakes
What we see most often in portals across Chile and Latin America
Announcing the change before holding access, keys and code.
Removing the partner's users without reassigning records or reviewing workflows.
Rotating a token without notice and breaking an integration mid-operation.
Finding out the integration ran on a provider server that no longer exists.
Want to know if this applies to your case?
Book a 30-minute diagnostic30 minutes with Roberto. No demo and no access to your CRM.
How we solve it at Revenue Hub Latam
An orderly handover in 30 days
We run the handover in parallel with your operation: access and keys, inventory, alerts and plan in four weeks. Everything that exists is documented in your name, and afterwards we run your HubSpot with written response times. We compare by model and never name your current provider.
Switch partners
A 30-day handover: access, inventory, alerts and plan, without stopping your operation.
See the handoverSupport and operations
After the handover, Managed or Dedicated HubSpot with written response times.
See operations plansHubSpot Diagnostic
If you first want to know what you have, 10 hours of inventory with risks and backlog.
See the Diagnostic
The guarantees that apply
- It’s yours.
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
- Alerts.
An automatic alert tells you if an integration or form stops bringing in data. You hear it from us first.
We put them in writing because they are what we control.
Straight answers
Frequently asked questions
What if my partner does not hand over the code?
Inventory what runs in your portal, document what depends on third-party servers and rebuild only what is critical. Meanwhile, turn on alerts to know if something stops working.
Can the partner be removed without losing their records?
Yes. Deactivating a user stops them from logging in, but their records and history stay in the CRM. Before removing them, reassign the records they own.
What happens to integrations when a token is rotated?
Those using the old token stop working when it expires. HubSpot lets you expire it immediately or in 7 days: use that window to update each integration.
How do I see who installed each app?
Under Settings > Integrations > Connected Apps. Every app shows its status, install date, who installed it and its last activity.
How long does an orderly handover take?
About four weeks for access, inventory, alerts and plan, in parallel with the operation. If structural debt shows up, it is solved afterwards with a fixed scope.
Who writesRoberto Guerra
Designs the CRM architecture, integrations and operation of each account. He writes these guides from what he sees every week in HubSpot portals of B2B companies across Chile and Latin America.
Meet the team30 minutes with Roberto.
We review one concrete problem, its impact and your starting point. No demo and no access to your CRM.