HubSpot migrates all custom assistants to Breeze projects on July 13, centralizing AI builds in Studio
HubSpot is converting all existing custom assistants to read-only and migrating them into Breeze projects on July 13, 2026, shifting day-to-day AI builds and governance into Breeze Studio. The change is documented in HubSpot’s Breeze overview and reinforced in the Studio documentation, which both call out the July 13 migration date.
HubSpot Breeze migration makes custom assistants read-only on July 13, 2026
HubSpot’s guidance states that “on July 13, 2026, existing custom assistants will be read-only and automatically migrated to Breeze projects,” with teams managing them going forward inside Breeze Studio. That timeline appears in the English-language Breeze overview and is mirrored in the Spanish-language version that notes the same July 13 cutoff for read-only status and automatic project creation under Breeze (Comprender Breeze).
Breeze Studio centralizes AI assistants, agents, and context
Breeze consolidates how AI behaves across the HubSpot account by letting admins configure behavior, instructions, and approved information sources from a single place. After the migration, teams shape responses and guardrails in Studio rather than in scattered ad hoc assistants, as described in the Studio how-to for assistants and agents. In practice, this centralization reduces drift between teams, makes audit trails clearer, and simplifies change control when legal or brand guidance updates.
What teams should check after the migration
Most assistants will reappear as named Breeze projects. Expect them to be locked for editing in their old locations and editable only within Studio. Partners tracking the rollout have flagged small housekeeping items, such as manually porting welcome messages and conversation starters, which are called out in roundups like this implementation advisory and a Spanish-language migration note. In practice, it’s worth scheduling a quick post-cutover sweep to confirm assistant names, owners, and knowledge sources are set as intended in each Breeze project.
Why this matters for governance and AI quality
Centralizing assistants into Breeze projects gives admins one place to set role-aware context and approved content sources so AI outputs stay on-brand and compliant. HubSpot’s description of Breeze emphasizes response generation grounded in relevant CRM data and curated sources, which is easier to enforce in Studio than across one-off assistants spread around the portal, as explained in the Breeze overview. For most teams, the immediate impact is less thrash in AI behavior, fewer “rogue” prompts, and simpler reviews when security or legal needs to validate how an assistant was configured.
Share With Others
