HubSpot Closes Legacy Private-App Creation for New Accounts; Older Accounts Face Oct. 26 Cutoff

HubSpot’s published schedule now bars accounts created on or after September 28, 2026, from creating legacy, non-Projects private apps through the account interface. Accounts created earlier face an October 26 cutoff for creating them, according to HubSpot’s creation notice.

For teams connecting HubSpot CRM data to reporting software or building an app that responds to CRM events, the change affects how a new integration is set up. It does not immediately disable private apps already in use or end access to the CRM.

Choose the replacement by what the integration does

For an account-level REST API connection, such as pulling CRM records into a reporting system, HubSpot describes Service Keys as scoped credentials. They remain in public beta. A Service Key cannot authenticate webhooks or power UI extensions; integrations requiring those features call for a Projects-based app.

That distinction gives administrators a useful first question: does the connection only make API requests, or does it also receive event notifications or add interface features? The answer determines whether a Service Key fits the job or the integration needs an app built with Projects.

Existing apps have a later deadline

The creation cutoffs are separate from a migration requirement. In a September 15 notice, HubSpot said existing legacy private apps must migrate to the Projects-based model by September 2027. It did not give an exact day that month.

Teams commissioning a new connection can choose its authentication method against the features it needs. Teams running a legacy private app can keep the creation cutoff distinct from the longer-term work of migrating that app.