HubSpot 2027 Readiness Audit
HubSpot is retiring legacy apps and older APIs. Know what in your portal depends on them.
A fixed-price audit of your integrations and workflows. You get a clear plan to migrate before support ends in September 2027, and to get your automation ready for HubSpot’s new workflow builder.
See what’s included ↓ · Not ready for a call? Take the 5-minute self-audit
At a glance
- From $600, fixed price
- Integration check in every package
- Read-only review: nothing changes without your OK
- Plan ordered by deadline and risk
- Migration and cleanup quoted separately
The dates that matter
HubSpot announced these changes at its Fall 2026 Spotlight. The migration window is already open.
Sept 15, 2026
Migration window opens
HubSpot announces the changes and gives customers and developers 12 months to move.
Oct 26, 2026
No new legacy private apps
Existing portals can no longer create legacy private apps. New in-account integrations use Service Keys instead.
March 2027
Replacement docs land
HubSpot plans to publish replacement documentation for every legacy API endpoint.
Sept 2027
Support ends
Legacy private apps and v1–v3 APIs become unsupported, with no bug fixes or security updates. HubSpot calls this the enforcement date.
The integrations nobody has looked at in years are usually the ones that matter.
The sync from your billing system. The script that feeds leadership’s dashboard. The custom code inside the workflow that routes every new lead. If they were built on a legacy private app or an older API, they need a new home before support ends.
What the audit looks for
- Legacy private apps, and what each one connects to
- Webhook subscriptions that will need a private app on the new platform
- Custom-coded workflow actions that use a legacy app token or an older API client
- Workflow webhooks and scripts that call v1–v3 endpoints
- Connected marketplace apps, so you can confirm each vendor’s plan
Data-only connections move to Service Keys
BI tools, warehouse syncs and internal scripts. Service Keys are created in your HubSpot settings, scoped to what each connection needs, logged, and can be rotated without rebuilding the integration.
Webhooks and app cards need a new private app
Anything that listens for HubSpot events or shows a card inside a record needs a private app built on HubSpot’s new developer platform. These take more work, so they go early in the plan.
While I’m in there: your workflows.
Two more HubSpot changes make this a good time to know exactly what your automation does, and what it costs to run.
A new workflow builder is in beta.
HubSpot opened its new builder as an opt-in beta in September 2026. Moving everyone over is likely months away, but converting a workflow can’t be undone, so it pays to know what you have first.
Pricing is moving toward credits.
HubSpot is testing seat-and-credit pricing, where workflow actions use credits. So far it applies only to new customers in Europe, the Middle East and Africa. If it reaches your portal, duplicate or inefficient workflows could raise your costs.
Messy automation breaks during change.
Workflows that overlap, conflict or rely on outdated properties are the most likely to fail during a migration.
What you get
Four deliverables that show what your portal depends on today and what it needs next.
1. Integration and app inventory
Every legacy private app, connected app, webhook and older API call: what it does, what depends on it, and the right migration path for each.
2. Workflow inventory and map
Every active workflow documented, from trigger to actions to what it touches, plus a diagram of how your workflows trigger, feed or overlap with each other.
3. Performance review
How each workflow is performing, and where workflows are underused, redundant, producing errors or using more actions than they need.
4. Audit overview and action plan
What to migrate first, what to clean up, consolidate or retire, and what it will take to move your automation to the new builder.
One fixed price
Based on how many active workflows your portal has. The integration check is included in every package.
Essentials
Up to 25 workflows- Integration and app inventory
- Workflow inventory and map
- Performance review
- Audit overview and action plan
Standard
26–50 workflows- Integration and app inventory
- Workflow inventory and map
- Performance review
- Audit overview and action plan
Advanced
51–100 workflows- Integration and app inventory
- Workflow inventory and map
- Performance review
- Audit overview and action plan
Custom
More than 100 workflows- Integration and app inventory
- Workflow inventory and map
- Performance review
- Audit overview and action plan
Active workflows only. Inactive workflows count toward your total only if you want them reviewed. Not sure of your count? I’ll confirm it with a quick look at your portal before you commit. Planning, not migration. Migration, cleanup and conversion work is quoted separately, based on what the audit finds.
How it works
- Short call. We confirm your workflow count, your hubs and the tools you know connect to HubSpot.
- Access. You give me access to your portal, and I review it without changing anything.
- Review. I start from HubSpot’s own legacy app and API migration flags, then trace every integration and active workflow.
- Plan. You get the four deliverables, with what to do first based on deadline and risk.
- Your call. Your team can work from the plan, or I can quote the migration and cleanup.
What I’ll need from you
- Which HubSpot hubs and tiers you have
- Access to your portal. I’ll send step-by-step instructions.
- The tools you know connect to HubSpot: billing, ERP, website, data warehouse, Zapier and so on
- Who built your integrations, if you know
I’ll tell you if you don’t need me.
If the audit shows your integrations are already on solid ground and your workflows are in good shape, the report will say so.
Questions
Will my integrations stop working in September 2027?
HubSpot says legacy private apps and v1–v3 APIs will be unsupported from September 2027. That means no bug fixes, reliability improvements or security updates, and HubSpot calls that date its enforcement date. It hasn’t said exactly what happens to calls after that, which is a reason to move early rather than wait and see.
How do I know if I have legacy private apps?
In HubSpot, go to Development, then Legacy apps. HubSpot also flags older API usage under Development, then Migrations. The audit goes further: what each app does, what depends on it, and where it should move.
What is the difference between a Service Key and a private app?
A Service Key is an account-level credential for connections that only read and write data, like BI tools, warehouse syncs and scheduled scripts. You create it in HubSpot settings. A private app on HubSpot’s new developer platform is a full app project. You need one for webhooks, app cards and other features that a Service Key can’t do.
We use marketplace apps. Are those affected?
Marketplace apps are their vendors’ responsibility, and HubSpot requires vendors to move to the new platform to stay listed and certified. The audit lists every connected app so you can confirm each vendor’s plan.
Do you do the migration?
Not as part of the audit. The audit tells you what to migrate, fix and convert. That work is quoted separately, based on what the audit finds and your priorities.
Will you change anything in my portal during the audit?
No. I look, document and recommend. Nothing changes without your OK.
Know where your portal stands before the deadline does.
Start with a short call. I’ll confirm your workflow count with a quick look at your portal before you commit.