What This Update Actually Is
HubSpot is officially deprecating the Pipelines API V1. The end-of-life date is November 2, 2026.
"Deprecation" means HubSpot will stop supporting and serving V1 API requests entirely. It's not a soft sunset. There's no grace period after the date. If your code calls a V1 Pipelines endpoint on November 3, you'll get an error.
The Pipelines API is what developers and operations humans use to programmatically create, read, update, and delete sales pipelines and pipeline stages. That includes deal pipelines, ticket pipelines, and any custom pipeline objects you've built.
V3 has been available for some time. This deprecation is HubSpot officially closing the door on the older version.
Why HubSpot Shipped This
API versions don't get deprecated arbitrarily. V1 was built when HubSpot's platform was fundamentally different. The data model has grown. The object framework has matured. Maintaining a legacy API version alongside a modern one creates inconsistencies, security surface area, and developer confusion.
V3 aligns the Pipelines API with HubSpot's broader CRM API standards. That means consistent authentication patterns, consistent error handling, and consistent object references across everything else you're building on the platform.
The external problem is straightforward: old code breaks. The internal frustration we hear from ops humans is messier. Nobody wants to dig through three years of integration code, half of which was written by someone who no longer works at the company. We get it. That's exactly why this article exists.
How to Use It Step by Step
Here's a practical migration path. You don't need to do all of this in one sitting, but you do need to start now.
- Audit every integration and app connected to your HubSpot portal. Check your HubSpot connected apps list (Settings, Integrations, Connected Apps) and your private app scopes. Look for any app calling crm/v1/pipelines endpoints.
- Check your custom code actions. If you use workflows with custom code steps or any serverless functions, search your codebase for "v1/pipelines" or "pipelines/v1".
- Review third-party integrations. If you use a middleware tool like Make, Zapier, or a custom-built connector, confirm with the vendor whether their HubSpot pipeline steps use V1 or V3. Don't assume they've already migrated.
- Read the Pipelines API V3 documentation on HubSpot's developer site. Map the V1 endpoints you're using to their V3 equivalents. The core objects are similar, but request structures, property names, and response shapes differ.
- Update your private apps' scopes if needed. V3 may require different permission scopes than your existing private app is configured with.
- Test in a sandbox or developer account before pushing to production. HubSpot developer accounts are free and let you validate V3 calls without risking live pipeline data.
- Set a hard internal deadline for completion. November 2 is the external deadline. Set your internal deadline for October 1 at the latest. You want buffer.
What It Touches in Your HubSpot Strategy
On the surface, this looks like a developer task. It's not only that. It touches your go-to-market operations more broadly than most teams realize.
Pipeline data is foundational. Deal stages power your revenue forecasting. Ticket stages power your service SLA reporting. If a V1-dependent integration breaks, it doesn't just throw an error. It can stop stage updates from syncing, corrupt historical stage data, or silently fail while your team thinks the system is working.
Key Takeaway
A broken Pipelines API integration won't always alert you loudly. Stage sync failures can look like data entry issues. Audit your integrations before the deadline, not after something goes wrong.
Here's what's potentially at risk if you miss the migration:
- Sync pipeline stages from external CRMs or ERPs that write to HubSpot via the API.
- Custom reporting tools that pull pipeline structure to build external dashboards.
- Provisioning scripts that create or update pipelines and stages when onboarding new business units or franchises.
- Revenue operations automations that trigger off stage changes and read pipeline configuration programmatically.
If you're building or managing pipeline rules programmatically, this migration pairs directly with a recent update worth reviewing: HubSpot's public API for CRM pipeline rules. That update covers managing stage editing permissions, deal approvals, and backwards movement via API, all of which become more useful once you're on V3.
Key Takeaway
If your portal has been set up for more than two years and you've ever had a developer or agency build custom integrations, there's a real chance you have V1 calls somewhere. Don't assume it's clean. Verify.
This isn't the only API-level change HubSpot is shipping this cycle. The Payment Links API renaming update is another change that requires a code-level fix before a specific date. If you're doing an API audit for V1 pipelines, do a full integration review at the same time.
Who Should Care Most
This update is highly technical, but the humans who need to act aren't only developers.
- RevOps leads and HubSpot admins: You're the ones who need to coordinate the audit and own the deadline. Even if you don't write code, you need to know which integrations exist and who built them.
- Developers and technical consultants: You have a clear migration task. Start mapping V1 endpoints to V3 equivalents now while you have runway.
- Agencies and solution partners who built HubSpot integrations for clients: Check every portal you manage. Client portals often have legacy code from previous vendors. This is your responsibility to surface.
- Growing companies with complex CRM setups: If you've scaled beyond a basic HubSpot setup and brought in custom development along the way, you almost certainly have integrations to review.
- Small teams using only native HubSpot with no custom code: You can likely move on. If you've never had a developer connect anything custom to your portal, this deprecation doesn't affect your day-to-day use.
George's Take
I've been inside a lot of HubSpot portals over the years. One of the most consistent patterns I see is what I call integration debt. A developer built something clever two or three years ago, it worked, everyone moved on, and nobody documented it. Then something breaks and the scramble starts. This V1 deprecation is a gift if you treat it that way. It's a forcing function to do an integration audit you probably needed to do anyway. Don't wait until October. Start the conversation with your dev team or your agency this week. November 2 sounds far away. Portal audits always take longer than expected.
“Integration debt is quiet until it isn't. A hard deadline like November 2 is actually the best kind of motivation to clean up what's been lurking in your portal.”
While you're in cleanup mode, it's worth checking what else has shifted in your portal recently. Updates like inline report descriptions on dashboards are easy wins, but they're only valuable when your underlying pipeline data is trustworthy. Fix the plumbing first.
If you're not sure where your integrations stand or you want a second set of eyes on your portal before the deadline, let's talk. Our team has done this kind of audit dozens of times. We'll help you find what's at risk, map a migration path, and make sure November 2 is a non-event for your business. Book a strategy call at sidekickstrategies.com and we'll dig in together.
Frequently Asked Questions
What is the HubSpot Pipelines API V1 deprecation deadline?
HubSpot's Pipelines API V1 will be fully deprecated on November 2, 2026. After that date, any integration or application still making V1 API calls will stop working. There is no grace period after the deadline. All accounts using V1 must migrate to Pipelines API V3 before November 2, 2026.
Will the Pipelines API V1 deprecation affect my HubSpot account if I don't use custom integrations?
If you use HubSpot natively without any custom-built integrations, private apps, or third-party connectors that access pipeline data via API, you're not affected. The deprecation only impacts accounts where code is making direct API calls to V1 Pipelines endpoints. When in doubt, check your connected apps and private app settings.
What is the difference between HubSpot Pipelines API V1 and V3?
V3 aligns with HubSpot's modern CRM API standards, offering consistent authentication, improved error handling, and better compatibility with other HubSpot API objects. V1 was an older architecture that predates the current CRM framework. V3 covers the same core functionality but with updated endpoint structures and response schemas.
How do I know if I'm using HubSpot Pipelines API V1?
Check your codebase for API calls containing 'crm/v1/pipelines' or 'pipelines/v1'. Also review your HubSpot connected apps and private app scopes. If you use middleware tools like Make or Zapier with HubSpot pipeline steps, confirm with the vendor whether their integration uses V1 or V3 under the hood.
Where can I find the HubSpot Pipelines API V3 documentation?
The official Pipelines API V3 documentation is available on HubSpot's developer documentation site at developers.hubspot.com. Review the V3 endpoint reference and compare it to any V1 endpoints your integration currently uses before starting your migration. HubSpot also offers free developer accounts to test V3 calls safely.
What breaks if I don't migrate from Pipelines API V1 to V3 before November 2, 2026?
Any system making V1 API calls will receive errors instead of responses after November 2, 2026. This can break stage syncing from external tools, disrupt pipeline provisioning scripts, stop custom reporting that reads pipeline structure, and silently corrupt deal or ticket stage data. The impact depends on how your integration uses the pipeline data.
