HubSpot disables legacy public app creation as of June 23, 2026, completing the Projects-based shift
HubSpot shut off legacy public app creation for existing developer accounts on June 23, 2026, finalizing a two-step sunset and making Projects-based, CLI-driven development the only path for new public apps. The cutoff follows an earlier restriction for newly created developer accounts in May, and it means Marketplace-bound builds must now start with the Projects workflow rather than the old UI form, as outlined in HubSpot’s Legacy Public App Creation Sunset.
Projects-based app development replaces UI-built legacy apps
New public apps now have to be initialized with the HubSpot CLI using the hs project create workflow. In practice, that shifts core app setup and configuration into versioned source files like app-hsmeta.json and hsproject.json, and pushes feature add-ons (app cards, webhooks, serverless functions, and app pages) into a consistent project structure. Teams accustomed to creating apps in the Developer UI will find that the legacy “create public app” entry point is no longer available for eligible accounts after June 23.
Marketplace implications and what changes immediately
For Marketplace submissions, the practical change is where and how apps are created and maintained. HubSpot’s changelog confirms that existing legacy public apps keep working for now, but newly created public apps must be Projects-based as of June 23 for pre-May 26 developer accounts and were already restricted as of May 26 for newer accounts, per the sunset notice. That also means CI-friendly workflows, code reviews, and environment parity become the default for app teams targeting HubSpot’s Marketplace rather than ad hoc UI-driven setup.
Migration path for existing public apps
If you’re carrying legacy public apps, HubSpot provides a documented route to move them onto the new framework via the migrate an existing public app guide. The guidance maps legacy configuration into Projects artifacts and brings apps forward to current platform versions. For net-new builds, HubSpot’s developer docs detail the Projects-first flow and recommended commands, starting with the CLI-based create a new app path.
Why it matters for partner roadmaps and engineering workflows
This cutover tightens release hygiene for HubSpot app teams. Source-controlled app configuration, explicit feature manifests, and CLI-first deploys reduce configuration drift and simplify reviews. The trade-off is that partners and internal platform teams need to align on Projects-era conventions, ensure developers are on current CLI versions, and update Marketplace readiness checklists to reflect Projects-only app creation going forward. Independent developer resources have been flagging these deadlines for weeks, including an explainer that tracks the May 26 and June 23 enforcement dates in a Projects CLI checklist built for the 2026 sunset.
Share With Others
