topic Re: Should I migrate my private legacy app? in APIs & Integrations

Should I migrate my private legacy app?

FHulleman — Mon, 16 Feb 2026 15:29:01 GMT

Hi,

I have a very simple Hubspot CRM contacts integration in my PHP Laravel 12 project. I only use the post contact endpoint to create new contacts. And I currently only have a legacy private app in Hubspot > developers which provides me with an API token and the right scopes.

Since now it is marked as 'legacy': how long will i be able to keep on using this private legacy app?

And when I read this migration documentation it seems to assume that I already have a hubspot app with hsproject.json & app.json files. But since I only use 1 endpoint with my API key, I don't have a hubspot project with these json files.

Preferably I would like to migrate my private legacy app to the new project framework in Febraury or March, so I won't run into suprises in a couple of months or next year.

Good to mention: in the near future I'm about to implement hubspot webhook handling in my laravel 12 project, so I can sync some of my database tables, when contacts are updated in Hubspot.

Can you explain (or send me a link to the right documentation) what I should do to update my laravel 12 project to work with the new project framework?

Re: Should I migrate my private legacy app?

SteveHTM — Mon, 16 Feb 2026 17:39:42 GMT

@FHulleman - You are not alone in being baffled by the opaque approach to this transition. The use of simple API key integration like yours (and mine) is entirely unaffected by this developer platform transition, which is still working out its kinks. The re-labelling of Private to Legacy apps is seeminly part of some grander plan yet to be revealed - I'm hoping it's all positive.

The only related topic that has come to light recently is the introduction of Service Keys (in Beta) which replicates what we used to see under Private apps. I guess there is a transition in futur,, but it is awkward at best today.

Hope this is helpful.

Steve

Re: Should I migrate my private legacy app?

GRajput — Wed, 25 Feb 2026 12:35:48 GMT

Hi @FHulleman

HubSpot’s documentation around legacy versus new Private Apps is not entirely clear, but the recommended approach is to create a new (non-legacy) Private App by navigating to Settings → Integrations → Private Apps in your HubSpot account.
When creating the app, ensure that you assign all the required scopes (such as contact read/write permissions) and then generate a new access token.

The newly generated access token functions the same way as the legacy token you are currently using. You can simply replace the old token in your application configuration with the new one, and your existing API integration should continue to work without requiring any structural changes.

I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.

Thanks!