What This Update Actually Is
HubSpot's Multi-Account Management (MAM) lets enterprise organizations mirror CRM data, contacts, companies, and more across multiple HubSpot portals. Until now, mirroring was all or nothing for the objects you chose to share.
This update changes that. Super admins can now mark individual contacts or companies as excluded from cross-account data mirroring. A new property called "Excluded from cross-account data mirroring" lives inside a property group called Multi-Account Management. Flip it on for a record, and that record stays put. It won't travel to your connected accounts.
Bulk actions are supported too. Super admins can use the existing bulk property edit framework to exclude dozens or hundreds of records at once. All HubSpot users in the portal can view the new property, but only super admins can change it.
Why HubSpot Shipped This
Here's the real problem this solves. Multi-Account Management was built for organizations running multiple business units, regions, or brands inside HubSpot. The promise: one shared CRM layer, less duplicate data entry, cleaner collaboration.
But that promise had a catch. Some contacts don't belong in every account. A confidential prospect tied to an acquisition. A partner contact for one division only. A person under a legal hold who can't be shared outside a specific team. When mirroring was binary, organizations had to choose between using MAM broadly and keeping sensitive records safe.
That tension is real. We've seen it across portals with multiple business units: admins either avoid MAM entirely or build elaborate workarounds to quarantine records. HubSpot shipping selective exclusions removes that tension and lets more organizations confidently run MAM at scale.
How to Use It Step by Step
- Confirm you're a super admin in the portal where MAM is configured. Standard admins can view the property but can't edit it.
- Navigate to the Contacts or Companies index in your CRM. Find the record you want to exclude from mirroring.
- Open the record and look for the property group labeled Multi-Account Management. Inside it, find the property "Excluded from cross-account data mirroring."
- Set the property value to exclude that record. The record will no longer mirror to connected accounts.
- For bulk exclusions: go to the Contacts or Companies index, filter or select the records you need to exclude, then use the bulk property edit action to set the exclusion property across all selected records at once.
- Document your exclusion criteria in your data governance notes. Future admins will thank you. Explain why specific records are excluded, not just that they are.
What It Touches in Your HubSpot Strategy
This update ripples outward from a single property into several parts of how your organization governs its CRM. Here's where it lands.
Data governance and compliance workflows: if your organization runs under GDPR, HIPAA, or internal data classification policies, this property becomes a compliance control point. You can now tie exclusion logic to your existing data handling procedures.
Automation workflows: because this is a standard HubSpot property, you can trigger workflows off it. Set up an enrollment trigger based on a contact's lifecycle stage, deal sensitivity, or a custom classification property, and auto-set the exclusion flag. That's how you make compliance scalable without manual review of every record.
Key Takeaway
The exclusion property is a real HubSpot property, which means workflows, lists, and reports can reference it. Build automation around your exclusion logic so it runs without manual intervention.
CRM data health and portal audits: if you run regular portal audits, add a check for the Multi-Account Management property group. Confirm excluded records are intentionally excluded and that the exclusion criteria are documented. This is now a standard audit item for any MAM-enabled organization.
If you're not already running structured audits of your portal, our HubSpot portal audit checklist covers 70+ items, including data quality and property hygiene. This new MAM property belongs on that list now.
Reporting and list segmentation: you can build active lists of excluded records for reporting. This gives legal, compliance, or executive teams a live view of what's protected without needing to query a data warehouse.
Key Takeaway
Don't treat this as a one-time toggle. Build a living list of excluded records, assign ownership to a specific admin role, and review it quarterly. Selective mirroring only stays clean if it's actively maintained.
This update also fits a broader pattern HubSpot has been building: giving admins more property-level precision over how data behaves. The Data Agent optional tokens update is another example of that shift, letting you control exactly which records AI enrichment touches.
Who Should Care Most
Not every HubSpot user needs to act on this today. But for specific organizations, it's a significant capability unlock.
- Prioritize this immediately if you run multiple HubSpot accounts for different business units or brands and have compliance requirements around data sharing. You've been waiting for this.
- HubSpot super admins at Professional or Enterprise tier across any hub (Marketing, Sales, Service, Content, Data, Commerce, Smart CRM). This property is available across all of them.
- RevOps and data governance leads who've been managing exclusions through workarounds like separate pipelines, manual lists, or custom code. This is your clean solution.
- Organizations in regulated industries: healthcare, legal, financial services, or any space where certain records carry sensitivity flags that govern where data can live.
- Companies considering MAM adoption: if you've held off on Multi-Account Management because you couldn't control sensitive records, this update removes one of the most common objections.
If you're a single-portal organization with no MAM setup, this update doesn't affect your current workflow. File it for future reference and move on.
George's Take
I've sat in too many portal reviews where the conversation about Multi-Account Management stalls at the same place: "We love the idea, but we can't let everything mirror." That's not a technology problem, that's a control problem. And HubSpot just handed admins the control they needed. What excites me most isn't the property itself; it's that this property is automation-friendly. The humans running complex multi-account portals can now build a governance workflow that enforces exclusion rules automatically, without someone manually reviewing records before every sync. That's the kind of infrastructure that lets growing organizations scale MAM without scaling their admin headcount alongside it.
“The humans running complex multi-account portals can now build a governance workflow that enforces exclusion rules automatically. That's infrastructure, not just a feature.”
This fits a broader pattern we've been tracking. As covered in our breakdown of HubSpot's recent wave of 34 updates, HubSpot is consistently moving toward cleaner data and more granular admin control. Selective mirroring is exactly that pattern applied to multi-account infrastructure.
If your organization is running MAM or evaluating it, the right move is a structured review of which records should be excluded and why, before you flip this on at scale. That's where having a clear governance framework matters as much as knowing where the property lives.
Want a second set of eyes on your multi-account setup or your CRM data governance strategy? Book a strategy call with the Sidekick team. We'll help you build the exclusion logic, the workflow automation, and the audit cadence so this capability actually protects your data instead of just sitting in a property group.
Frequently Asked Questions
What is selective mirroring in HubSpot Multi-Account Management?
Selective mirroring lets super admins exclude specific contacts or companies from cross-account data sharing in HubSpot's Multi-Account Management. A new property called "Excluded from cross-account data mirroring" controls this at the record level. Excluded records stay in the originating account and don't sync to connected accounts.
Who can change the "Excluded from cross-account data mirroring" property?
Only super admins can edit the exclusion property. All other HubSpot users with access to the portal can view it, but they can't change its value. This keeps data governance decisions in the hands of the humans responsible for cross-account configuration.
Can I bulk-exclude contacts from HubSpot data mirroring?
Yes. Super admins can use HubSpot's existing bulk property edit feature to set the exclusion property across multiple contacts or companies at once. Select the records from the index view, choose the bulk action, and update the Multi-Account Management property for all selected records in one step.
Does this update affect all HubSpot hubs?
Yes. Selective mirroring in MAM is available for Professional and Enterprise tiers across Commerce Hub, Content Hub, Marketing Hub, Data Hub, Sales Hub, Service Hub, and Smart CRM. It applies to contact and company objects in any portal where Multi-Account Management is active.
Can I automate the exclusion of records from data mirroring using workflows?
Yes. Because "Excluded from cross-account data mirroring" is a standard HubSpot property, you can use it in workflows. Set up enrollment triggers based on deal sensitivity, lifecycle stage, or a custom classification, then auto-set the exclusion property. This makes compliance enforcement scalable without manual review.
Should I use selective mirroring if I only have one HubSpot portal?
No. Selective mirroring only applies when Multi-Account Management is active, which requires multiple connected HubSpot portals. If you're running a single portal, this property has no effect on your current setup. It's worth understanding if you're planning future expansion into a multi-account structure.
