HubSpot Sets October 26 Deadline to Disable Legacy Private Apps

HubSpot forces integration migration with six-week window

HubSpot disabled creation of legacy private apps for accounts created after September 28, 2026, and will extend the restriction to all existing accounts on October 26, 2026. The change affects custom CRM integrations, enrichment pipelines, billing systems, data warehouses, and internal RevOps tooling that rely on private-app credentials. Organizations standardized on HubSpot have six weeks to inventory API dependencies, migrate authentication methods, and validate third-party applications.

The timing coincides with HubSpot's introduction of centralized Price Books, which allow RevOps teams to manage product pricing and apply it directly in the deal line-item editor. The combination narrows part of the functionality gap with Salesforce CPQ and Microsoft Dynamics 365, but the private-app restriction increases migration friction relative to platforms that continue to support broader custom-app models.

Buyers should budget for an inventory of all private-app credentials, engineering work to migrate integrations, security review of replacement authentication methods, and testing of pricing, quoting, and downstream billing flows. HubSpot has not disclosed a migration fee, affected-customer count, or API-volume threshold, so the financial impact must be assessed account by account. The development increases the importance of contractual language covering API access, deprecation notice, migration support, and integration limits.

Salesforce reports $1.5 billion Agentforce ARR

Salesforce crossed $1.5 billion in annual recurring revenue for Agentforce, signaling that autonomous and assisted AI agents have moved from experimental CRM add-on to a material commercial product line. The figure provides a stronger revenue-validation signal than Microsoft Copilot, HubSpot Breeze, or AI-native sales platforms such as Gong, Outreach, and Apollo, which have announced agent capabilities without disclosing comparable commercial traction.

The ARR figure does not establish customer-level ROI, deployment scale, gross retention, or agent accuracy. Procurement teams should request Agentforce-specific pricing and consumption assumptions, number of production deployments rather than trials, human-escalation and error rates, data-residency and permission controls, and measured productivity or conversion improvements by workflow. Buyers should treat Agentforce as a potentially separate budget category within CRM, automation, and customer-service spending.

HubSpot's Agent Builder reaches 2,700 beta customers

More than 2,700 customers activated HubSpot Agent Hub and Agent Builder during the beta quarter. The tools entered public beta for all Pro and Enterprise customers on July 23, 2026, and HubSpot introduced an Agent CLI usable inside Codex, Claude Code, and Claude Cowork. The adoption figure is a useful signal, but it is not equivalent to paid production usage or documented ROI.

Buyers should distinguish activated beta accounts from paying customers, agent creation from successful autonomous execution, and usage volume from measurable pipeline, service, or retention gains. For enterprises already standardized on HubSpot Pro or Enterprise, the feature expansion could reduce the need for point tools from Intercom, Gong, Outreach, or Apollo. Organizations with strict governance requirements should validate model providers, data access, prompt logging, human approval controls, and whether agent activity is included in existing subscription limits or charged separately.

What to watch

The October 26 deadline creates immediate procurement risk for HubSpot customers. Organizations should prioritize integration audits over new feature evaluation. The private-app restriction may also signal broader platform governance changes as HubSpot competes with Salesforce's Agentforce and Microsoft's Copilot Studio.

Salesforce's $1.5 billion Agentforce ARR validates enterprise demand for AI agents inside CRM, but the lack of disclosed accuracy, escalation rates, or ROI benchmarks means buyers must establish measurement criteria before deployment. The gap between reported ARR and published performance data should inform contract negotiations, particularly around service-level agreements, refund provisions, and consumption caps.

RevOps headcount growth—estimated at 174,000 open roles between June 2025 and July 2026—supports continued platform spending, but it also means buyers should evaluate whether an AI product genuinely removes manual work or simply adds another administration layer. A large RevOps workforce can support sophisticated deployments, but it does not eliminate the need for measured productivity gains.