How to move every user from one group to another with Bulk Group Change

Reassigning agents one record at a time is fine for a handful of people. When you need to move a whole team, VICIdial gives you Bulk Group Change — the last sub-menu option under the User Groups section. It reassigns every member of one User group to another in a single action, so you never have to open each agent's record. On a floor of any real size, this is the difference between a thirty-second admin task and an afternoon of clicking.

It is worth being clear about what a group membership actually carries before you move anyone. A user group is not just a label for reporting; it bundles allowed campaigns, allowed call times, QC scope, the webphone overrides, and the report boundaries a manager sees. When Bulk Group Change moves an agent, it moves all of that along with them. So the question to ask first is never just where do these people go, but does the destination group already have the settings these people need.

The two options

• Change one user group to another — pick a source group and a destination group, and every Agent currently in the source moves to the destination.
• Change all non-ADMIN user group users to another user group — sweep everyone who is not in the ADMIN group into a single destination group, leaving your administrators where they are.

How the tool decides who moves

flowchart TD
  A[Open Bulk Group Change] --> B{Which option}
  B -->|One group to another| C[Pick source group]
  C --> D[Pick destination group]
  D --> E[All source members move]
  B -->|All non ADMIN| F[Pick destination group]
  F --> G{User in ADMIN group}
  G -->|Yes| H[Stays in place]
  G -->|No| I[Moves to destination]

When to reach for it

Bulk Group Change earns its place when a campaign wraps and you want to retire its group, when you reorganize teams, or when you are consolidating several small groups into one. Because a group carries reporting boundaries and permissions, moving agents also moves what they can see and which report cuts they fall under, so the change ripples further than a name swap. The second option — sweeping every non-ADMIN user into one group — is the blunt instrument you reach for when you are flattening a messy structure and want a clean slate, with your administrators deliberately left untouched so you do not lock yourself out of your own admin tooling.

One thing the bulk move does not touch is per-agent assignments that live outside the group, such as an Ingroup an individual agent was given by hand. If your team relies on those, plan to reapply them after the move or assign them at the group level so they survive future reshuffles. Checking this before you commit saves a confusing first shift in the new group where agents are missing a queue they used to have.

Warning: the move applies immediately and there is no built-in undo. An agent in an active Agent session will not see their world change mid-call, but their next login lands them in the new group with that group's settings. Run bulk moves between shifts, and double-check the destination group's permissions before you commit.

If you would rather adjust the destination group's settings first, walk through modifying a user group before you sweep anyone into it. For the broader model of how teams map to groups, see our users and groups guide.

Running a busy floor with shifting teams? See VICIfast plans for a dedicated VICIdial server that is ready in under 40 seconds.