Paste a list of names — get a Bulk Admin Tool-ready end-user CSV with unique user IDs, PINs, passwords, and sequential extensions. Upload straight into CUCM.
The CUCM BAT CSV Generator (Users) takes a pasted name list and builds a complete Bulk Administration Tool end-user CSV — column headers, safe user IDs, unique sequential extensions, random 8-digit PINs, and reasonable defaults for department, locale, and profile. It's the tool we reach for when a merger or mass-hire event turns up and the alternative is hand-editing 200 rows. The CSV matches the default BAT template format from CUCM 10.5 through 15, so you can upload it as-is and run an Insert Users job without touching the format.
Paste names, set a starting extension, click Generate CSV.
Don't delete or reorder the header row. BAT matches columns by name, not position, but your template in CUCM must list the same columns.
If you have two Jane Does, the tool appends 2 to the second. Inspect the CSV before upload — you'll usually want jane.doe and jane.doe2 and not jdoe2.
The generator emits a random 8-digit PIN per user. If you carry a password policy that requires rotation after first login, tell end users to reset through the Self-Service Portal or LDAP.
Bulk Administration has been part of CUCM since 5.x and is still the fastest way to insert, update, or retire users in bulk. The interface looks dated, but under the covers it's the same tool that handles thousands of records per minute in large healthcare deployments. When BAT fails, it's almost never BAT's fault — it's a column header mismatch, a missing device association, or an LDAP sync overwriting your work. This tool emits a CSV that uses BAT's canonical column names and only the minimum fields required for a clean insert. You can delete columns you don't need; you should not rename them.
The user-insert workflow is deliberately three steps: upload the CSV to CUCM, run an Insert Users job, verify the Job Scheduler log. The log calls out the row number on every failure — 99% of failures fall into three buckets: duplicate user ID, missing Primary Extension device, and Locale name mis-spelled. The generator defaults to English United States because that string is the only one that always exists on a clean CUCM install. If your cluster has been internationalized, sync the list to the names shown in CUCM Admin → User Management → User Settings → User Locale.
We deliberately do not emit the Primary Extension column. In BAT terms that field is the DN string followed by a partition, and getting the partition wrong creates ghost DNs in CUCM that have to be cleaned up by hand. The safer workflow is: insert users with this CSV, then associate devices + extensions in a second BAT job (the phone CSV generator is our next tool in the list). If you need to pre-populate an extension, paste it in after generation — the column exists, we just leave it blank.
If you're operating in an LDAP-synced environment, this tool is for the outliers: service accounts, contractors, conference-room endpoints, and test users that never appear in AD. For the in-AD population, LDAP sync is still the right call — BAT user inserts will be rejected and you'll spend an hour chasing a User already exists error until you realize what's happening.
CUCM 10.5 through 15. If you're on 9.x, drop the optional columns (Extension Mobility CSS, Primary Extension) — BAT will accept the rest.
CUCM Admin → Bulk Administration → Upload/Download Files → Upload the CSV. Then Bulk Administration → Users → Insert Users → pick the CSV + matching template, preview, Submit. A BAT job appears under Job Scheduler.
No for synced users. Use this CSV for local-only outliers (service accounts, contractors, conference rooms) or for test clusters.
It sets the CUCM end-user web password. If you're synced to LDAP, leave it blank — LDAP is the password authority.
CUCM's default PIN policy allows ≥ 5 digits, but Unity Connection voicemail inbox security prefers 6–8. We default to 8 random digits so users have a working VM inbox from first login.
HR emails a spreadsheet of 22 names for Monday. LDAP syncs overnight; the voice team needs CUCM users ready before the phones arrive.
Branch expansion: 40 new conference rooms each need a CUCM end-user to own the room's Webex device license.
Lab cluster for a UCCX upgrade dry-run. Need 500 unique users to validate load.
The Network & UC Health Assessment is a written, independent review of your actual environment — not vendor marketing. Includes a bulk-ops playbook: templates, sample CSVs, and roll-back procedures for adds / moves / changes at scale.