Bulk Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Import/Export Menu

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/bat/15/cucm_b_bulk-administration-guide-15/cucm_b_bulk-administration-guide-1251su2_chapter_0111110.html

Published

2024-10-01

Updated

unknown

Accessed

2026-09-22

HTTP status

200

License

Cisco copyright; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Check Dependency on the export page selects dependent items only one level deep; items that a dependency itself depends on are not selected. in context
• Each CSV file inside the Import/Export tar is named after the configuration item it holds. in context
• Phone, Device Profile, Remote Destination Profile, Trunk, Gateway, SIP Profile, Softkey Template and Phone Button Template are export items in the Device Data group. in context
• The exported tar is downloaded through Bulk Administration > Upload/Download Files. in context
• When editing an exported tar, each CSV must keep its original file name and format, and any added file must use the exported name and format and be added to the header file. in context
• Cisco instructs that the User ID, User Pkid, Password and Pin fields in the exported enduser.csv must not be modified. in context
• The Import/Export export page groups items under System Data, Call Routing Data, Media Resources, User Data, Device Data and Advanced Features. in context
• Submitting an Import/Export export creates a job that runs immediately or later and is scheduled and activated through the BAT Job Scheduler. in context
• An Import/Export export is started from Bulk Administration > Import/Export > Export, where the administrator enters a tar file name and ticks the items to export. in context
• The Import/Export header file records the server the export was taken from, the time of the export, and details of the files in the package. in context
• An Import/Export export writes one log file for the overall transaction and one per exported item, with the item name prepended to the log file name. in context
• A re-tarred Import/Export file must keep the original directory structure because BPS looks for tar files at the default location only. in context
• CSS (Class of Control), Partitions (Class of Control), Time Period, Time Schedule, Route Pattern, Translation Pattern and Directory Number are export items in the Call Routing Data group. in context
• Route Group, Route List, Hunt List, Hunt Pilot, Line Group, Call Park, Call Pickup Group and Elin Group are export items in the Call Routing Data group. in context
• Import/Export writes password and PIN attributes to the exported files in encrypted form and does not support changing them to plain text. in context
• Device Pool, Location and Region are export items in the System Data group of Import/Export. in context
• In Unified CM 15 the Bulk Administration Import/Export export bundles the exported files into a .tar file that can be downloaded from the server. in context
• The Import/Export .tar file consists of a set of CSV files plus one header file. in context
• End User and Application User are export items in the User Data group of Import/Export. in context
• Voice Mail Pilot and Voice Mail Profile are export items in the Advanced Features group, not in Device Data. in context
• VPN details cannot be exported through Import/Export on the U.S. export unrestricted version of Unified CM, and the VPN checkboxes do not appear there. in context
• Cisco notes that tar -xvf may not work on a Windows server and suggests 7-Zip for tar and untar on Windows. in context
• Cisco's BAT guide does not publish the column layout of the per-item CSVs inside the Import/Export tar, so a reader of phone.csv, enduser.csv or device_pool.csv has to take columns from each file's header row rather than from a documented schema. inferred in context
• The Import/Export tar and the Phones or Users export CSVs are different artifacts, and a tool that reads the tar should not assume the Default Phone or All Phone Details column set documented for Phones > Export. inferred in context

Cite this source record

APA

WarmTransfer. (2024, October 1). Bulk Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Import/Export Menu. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-bat15-import-export-menu

BibTeX

@misc{warmtransfer-cisco-bat15-import-export-menu,
  title  = {Bulk Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Import/Export Menu},
  author = {{WarmTransfer}},
  year   = {2024},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-bat15-import-export-menu},
  note   = {Cisco Systems, accessed 2026-09-22}
}