Paste a list of users + DNs — get a BAT-ready CSV for Extension Mobility Device Profiles including button layout, line assignments, and login UserID mapping. Ready to import in minutes.
Extension Mobility lets users log in to any phone and bring their DN, button template, and CSS. The setup is tedious: one Device Profile per user, per phone model, with matching button assignments. BAT makes this bulk — if the CSV is correct. This tool emits a clean BAT-compatible CSV with the Device Profile Name, UserID, Phone Button Template, Softkey Template, Lines, Speed Dials, and User Locale populated per user.
Fill in your users, click Generate BAT CSV.
Bulk Administration → Upload/Download Files — upload the CSV.
User Device Profiles → Insert User Device Profiles → Validate.
Submit job; BAT creates profiles + assigns them to each UserID.
Three things fail post-import more than anything else. One: the UserID column doesn't match the CUCM End User's userid, so BAT creates the profile but can't associate it. Fix: always pull End User UserID from CUCM (or AD) as the source of truth. Two: the Phone Button Template referenced doesn't exist (typo or regional naming), so BAT uses Standard and nothing on the user's phone lights up the way they expect. Fix: create templates before uploading profiles. Three: the Partition or CSS referenced doesn't exist, so BAT quietly leaves those fields blank and the line doesn't route.
Validate in BAT before submitting — the validate step catches 80% of failures before they create orphan profiles. If validate reports warnings (not errors), fix the cause in the CSV, re-upload, re-validate. Never submit a job with unresolved warnings; the resulting orphans are painful to clean up.
For Extension Mobility specifically, the profile must match the phone model the user typically logs in on. A user with an 8851-profile cannot log in to a 7841 — the button counts don't match. If users roam across phone models, create multiple profiles per user (one per model) and name them UserID_8851, UserID_7841 so users can pick the right one.
Yes — the profile is model-specific. Cross-model roaming = multiple profiles per user.
Yes. Extend the per-user row with additional DN columns; BAT headers support up to 199 lines.
Phone = physical device config. Profile = portable config that gets loaded onto any phone at login.
BAT's Insert operation won't duplicate — failed rows report "already exists." Use Update instead if changing existing profiles.
New hires get 8851 profiles with one line, default template, default CSS.
100 Sales reps, all 8851, template FTEC_Sales_Template (3 speed dials pre-configured).
Some users roam between 8851 (desk) and 8841 (conference rooms). Two profiles per user.
Our UC Modernization Sprint plans + deploys Extension Mobility end-to-end — pilot, full rollout, and training included.