HubSpot's New App Version Rules Hit Agency Integrations

HubSpot's developer team confirmed in its own changelog that, as of November 2, 2026, apps must run on a supported developer platform version — currently v2025.2 or v2026.03 — to be listed or certified on the HubSpot Marketplace. Independent coverage from Martech Notes confirmed the same enforcement date and added a detail worth flagging for agencies: apps already undergoing certification or recertification get roughly 60 days to migrate, but new app listings built on an unsupported version are rejected outright, no grace period attached.

This is not a marketing-facing change. It will not show up in a client's dashboard or a feature release note. But for any firm that built a custom HubSpot app — a lead-routing integration, a client-facing data sync, a branded onboarding tool — on a client's behalf, it is a compliance clock with a real enforcement mechanism behind it, running on a part of the stack most marketing teams never look at.

What Actually Changed

HubSpot's Marketplace has required apps to declare a developer platform version for a while, but that requirement was mostly advisory for existing listings. The November 2 enforcement makes it binding: HubSpot's review pipeline now checks the declared platform version before an app can be listed or pass certification, and it rejects anything that falls outside the current supported set. The change affects Marketplace eligibility and submission timing specifically — an integration that still works perfectly for the client who uses it can nonetheless get blocked the next time it needs to be listed, updated, or recertified.

Why This Lands on the Agency, Not the Client

A client who commissioned a HubSpot integration two or three years ago has no reason to know what platform version it was built on, or that HubSpot's definition of "supported" has moved twice since launch. That knowledge sits with whoever built it — and if that was a contractor who has since moved on, or an in-house hire who left, the firm managing the client relationship now owns a deadline nobody is actively watching.

• Check the declared platform version on every client-facing HubSpot app your firm maintains, not just the ones scheduled for a feature update.
• Treat certification renewal as a trigger — an app coming up for recertification is exactly where the 60-day migration window starts ticking, whether anyone requested a review or not.
• Don't assume "it still works" means "it's still compliant" — a functioning integration and a listable one are now two different things under this policy.

This is the kind of ongoing platform maintenance that a dedicated SaaS development team is built to carry: someone whose job includes tracking changelog entries like this one and migrating a client's integration before a routine recertification turns into a dropped listing, rather than reacting to it after a client notices.

The Pattern Behind the Update

HubSpot has tightened Marketplace requirements more than once this year, and the direction is consistent: platform version compliance is becoming a standing gate, not a one-time cleanup exercise. Firms that treat a client's custom integration as a finished deliverable, rather than a maintained piece of software, will keep discovering these deadlines the hard way — usually when a client asks why their app disappeared from a dashboard.

If your firm built or maintains a HubSpot integration for a client and nobody has checked its platform version against this update, that is worth doing before the next certification cycle. If the audit turns up more than a quick fix, book a free consultation and we can help you scope what needs to change.