topic Re: Migrate legacy private app to Hubspot project in APIs & Integrations

Migrate legacy private app to Hubspot project

JerikaNguyen — Mon, 15 Sep 2025 07:01:44 GMT

Hi guys, I observe that Hubspot has updated a new feature called Project (to replace Private app - now called legacy app). I do have a question. My old legacy app script is running in Python script (Hubspot has support Python sdk). Now when I try to create hubspot project, it forces me to code in JS. I can't find document to init python project. Does the project feature require JS script only?

Re: Migrate legacy private app to Hubspot project

Jaycee_Lewis — Mon, 15 Sep 2025 21:50:28 GMT

Hi, @JerikaNguyen 👋 I don't think you are missing an option. As you noted, the documentation only offers JS options — Create an App. If you are using a different document, let me know, and I'll dig a bit more for us. — Jaycee

Re: Migrate legacy private app to Hubspot project

JerikaNguyen — Tue, 16 Sep 2025 06:49:02 GMT

My goal is to synchronize Contact, Company, and Association data.
I believe a private app access token is sufficient for this purpose.

However, I’ve noticed this is now referred to as a Legacy app, and I’m unsure how long HubSpot plans to continue supporting it and if I should migrate my flow from Legacy app to Project.
The Projects feature doesn’t seem to meet my requirements now.

Re: Migrate legacy private app to Hubspot project

Jaycee_Lewis — Tue, 16 Sep 2025 22:27:22 GMT

Hey, @JerikaNguyen the best place to stay on top of changes is to subscribe to the changelog. Upcoming features, as well as breaking changes and sunsets, are all announced there first. — Jaycee

Re: Migrate legacy private app to Hubspot project

RubenBurdin — Wed, 17 Sep 2025 14:47:43 GMT

Hi @JerikaNguyen , you’re right that the new HubSpot Projects feature only supports Node.js/JavaScript today. There’s no official option to initialize a Python-based project.

The SDKs for Python, Ruby, PHP, etc. remain fully usable with private apps (now labeled “legacy apps”), but the “projects” environment is a different execution layer that HubSpot manages, so it enforces JavaScript runtimes only (https://knowledge.hubspot.com/help-and-resources/how-to-use-the-hubspot-projects-tool )

If your flow is just syncing Contacts, Companies, and Associations, a private app access token is still valid and supported. HubSpot hasn’t published a sunset date for private apps, and they remain the recommended path when you need SDK flexibility or a language other than Node

(https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/overview )

Subscribing to the changelog is the best way to catch deprecation notices before they impact you.

If the only reason to migrate is concern over long-term support, I’d suggest monitoring HubSpot’s updates but keeping your Python integration running under the private app for now.

Projects will likely gain features over time, but at present they’re focused on hosted JS extensions, not general-purpose SDK use. If your real challenge is keeping those objects consistent across HubSpot and another system, Stacksync handles the two-way mapping automatically in real time, so you don’t have to recode workflows when HubSpot shifts its developer platform.