New-account cutoff
HubSpot disables legacy private-app creation on 28 September 2026 for accounts created on or after that date.
HubSpot · private apps · Service Keys
A HubSpot-backed routing checklist for admins and integration teams deciding how to replace new legacy private-app creation before the September and October 2026 account cutoffs.
Primary query: HubSpot legacy private app creation disabled September 28 October 26 2026 Service Keys · Updated 2026-09-07
Direct answer
HubSpot says new legacy private-app creation is disabled on 28 September 2026 for accounts created on or after that date and on 26 October 2026 for older accounts. Existing legacy private apps continue to work. For new system-to-system integrations that do not need webhooks, HubSpot directs customers toward Service Keys; integrations that need webhooks should use the Projects-based app path instead. The migration decision therefore starts with the integration capability, not with blindly converting every existing private app.
Practical sequence
Classify the target account by creation date so the applicable 28 September or 26 October 2026 creation cutoff is clear.
Inventory the integration’s purpose, required scopes, whether it is single-account or multi-account, and whether it requires webhooks.
Route simple account-level system-to-system integrations without webhooks toward a Service Key and keep the scope set to the permissions actually required.
Route integrations that require webhooks or broader app capabilities to the Projects-based app platform rather than assuming a Service Key can replace them.
Record the chosen path, owner, credential-rotation plan and acceptance test before the relevant cutoff; leave existing working legacy private apps unchanged unless there is a separate reason to migrate them.
Decision facts
HubSpot disables legacy private-app creation on 28 September 2026 for accounts created on or after that date.
For accounts created before 28 September 2026, creation is disabled on 26 October 2026.
Service Keys are intended for system-to-system integrations and do not support webhooks; webhook use requires an app path.
Boundaries
Free proof before paid workflow