What This Update Actually Is
HubSpot's user import feature got a meaningful upgrade. Before this change, you could only use import to create new users. That's it. If you wanted to update a seat type, move someone to a different team, change a permission set, or assign a manager, you had to do it manually, profile by profile.
Now, when you run an import from Settings > Users and Teams, HubSpot checks each row against existing users. If a match is found, it applies the changes. If the user is new, it creates them. The column mapping confirmation step and a post-import summary keep you in control throughout.
The four fields you can now update in bulk are seat type, team assignment, permission set, and manager. That covers the core of how access and reporting structure gets organized inside any HubSpot portal.
Why HubSpot Shipped This
If you've ever managed a HubSpot portal through a reorganization, a rapid hiring push, or a role restructure, you know exactly what this problem feels like. You've got a spreadsheet from HR with fifty updated records. And HubSpot only lets you apply those changes one at a time.
The frustration isn't just about time. It's about the mental load. Admins have to hold the full picture in their head, click into each profile, make the change, save it, and move on. Mistakes happen. Records get missed. Audits become guesswork.
HubSpot already gave us import for new users. Extending that to existing users closes the obvious gap. Now the import file becomes a single source of truth for user management, which is how mature RevOps teams prefer to operate anyway.
How to Use It Step by Step
- Go to Settings > Users and Teams in your HubSpot portal.
- Click the Import button. You'll see the same flow you'd use for new user creation.
- Prepare your CSV. Include the email address for each user (HubSpot uses this to match existing records), plus columns for whichever fields you're updating: seat, team, permission set, and/or manager.
- Upload the file and confirm your column mappings. HubSpot will map each column header to the correct user property. Review this step carefully, especially if your CSV uses custom column names.
- HubSpot processes the import. It identifies new vs. existing users automatically. New users get created; existing users get updated.
- Review the import summary. HubSpot gives you a breakdown of what changed, what was created, and any rows that couldn't be processed. Save this summary. It's your audit record.
One practical tip: run a smaller test import first. Pull five to ten existing users, make a minor change, and confirm the summary matches what you expected before you run the full file.
What It Touches in Your HubSpot Strategy
This update is scoped to Settings, but its ripple effect goes further than it looks. Here's where it actually lands in your broader portal structure.
Seat assignments connect directly to what features each person can access. Change a seat type incorrectly at scale and you can accidentally lock humans out of tools they depend on, or grant access that wasn't intended. Bulk import makes this faster, and faster means you need a clear plan before you run it.
Team assignments affect how data is segmented in reports. If your dashboards are filtered by team, a bulk team reassignment will immediately change what those reports surface. That's not a bug. It's the point. But it's worth knowing before you run the import.
Key Takeaway
Bulk-updating team assignments will immediately shift how team-filtered reports and dashboards display data. Audit your key reports before and after any large import to confirm the numbers reflect the new structure.
Permission sets determine what each person can see, create, edit, and delete across the CRM. Bulk permission changes carry real risk if your permission sets aren't clearly defined and named before you start. This update is a strong argument for cleaning up your permission set library first.
Manager assignments feed into HubSpot's reporting hierarchy. For sales teams using goal tracking and forecast reporting, having the right manager attached to each rep is more than an org chart detail. It affects rollup numbers at the leadership level.
Key Takeaway
If you manage a growing sales team and use HubSpot's forecast or goal tools, keeping manager assignments current in bulk is now dramatically simpler. Pair this import with a quarterly user audit cadence and your data hygiene stays sharp with minimal effort.
This pairs naturally with HubSpot's recent admin-focused updates. If you've been working through the redesigned Connected Apps and app owner management update, you already know HubSpot is investing in making portal governance cleaner for admins. User import updates fit that same thread.
Who Should Care Most
Not every portal needs this today. Here's who gets the most out of it right now.
- HubSpot admins managing 25 or more users who've handled reorgs or role changes manually. You've felt this pain directly. This update is built for you.
- RevOps leaders responsible for data governance. Bulk user changes with an import summary means you've got a paper trail for every change. Audits get easier.
- Growing companies in active hiring or restructuring phases. If your team headcount changed significantly in the last quarter, this lets you catch up on user structure without booking an afternoon for manual updates.
- Agency or partner admins managing multiple client portals. Standardizing a permission set across a client's team or correcting seat assignments after an onboarding handoff now takes one file instead of an hour of clicking.
If your portal has fewer than ten users and they rarely change, this won't move the needle for you today. But it's a habit worth building now before you need it.
George's Take
“The best admin tools aren't the flashy ones. They're the ones that quietly eliminate the work that was quietly wasting your team's time every single quarter.”
I've worked inside hundreds of HubSpot portals, and user management debt is one of the most common things we find during audits. Humans are in the wrong teams. Seats haven't been updated since the last reorg. Permission sets are named things like "New Permission Set 3" with no description. This update won't fix the naming problem, but it does remove the biggest friction point: applying corrections at scale. Pair it with a clear permission set naming convention, a quarterly user audit habit, and tools like workflow templates to standardize your ops processes, and you're building the kind of portal that actually supports growth instead of slowing it down.
If your portal's user structure is overdue for a clean-up, or you want a second set of eyes before running a bulk import, that's exactly what a Sidekick portal audit covers. Book a strategy call and we'll map out what needs to change and in what order.
Frequently Asked Questions
Can HubSpot user import now update existing users?
Yes. As of the July 20, 2026 private beta, HubSpot's user import tool can update existing users' seat types, team assignments, permission sets, and manager fields in bulk via CSV. Previously, import only supported creating new users. The system automatically detects whether each row is a new or existing user.
What fields can I update in bulk with HubSpot user import?
You can update four fields in bulk: seat type, team assignment, permission set, and manager. These cover the core of access control and reporting structure in HubSpot. Email address is used as the matching key to identify existing users in your import file.
Which HubSpot hubs and tiers does the user import update feature apply to?
This update is available to all HubSpot hubs and all tier levels, including Free, Starter, Professional, and Enterprise. It's currently in private beta for all accounts as of July 20, 2026.
Will bulk-updating team assignments affect my HubSpot reports?
Yes. If your dashboards or reports are filtered by team, changing team assignments in bulk will immediately shift what those reports display. This is expected behavior, not an error. Review your key team-filtered reports before and after any large import to confirm the data reflects your new structure.
How does HubSpot know whether to create or update a user during import?
HubSpot uses the email address in your import file to match against existing users in the portal. If a match is found, it applies the updated field values. If no match is found, HubSpot creates a new user. A post-import summary shows you exactly what was created, what was updated, and any rows that failed.
What's the best way to prepare for a bulk user import in HubSpot?
Start by cleaning up your permission set names so they're clear and easy to map. Build your CSV with an email column plus only the fields you're changing. Run a small test import of five to ten rows first and verify the summary before applying the full file. Save the import summary as your audit record.
