Source record · tier 2 current vendor documentation
Importing and Exporting Settings (Administering Avaya IP Office using Manager 12.3)
- Publisher
- Avaya LLC
- URL
- https://documentation.avaya.com/bundle/IPOfficeManager_12_3/page/Importing_and_Exporting_Settings.html
- Published
- 2023-03-08
- Updated
- unknown
- Accessed
- 2026-10-14
- HTTP status
- 200
- License
- Avaya proprietary documentation; no-redistribution; short excerpts and locators only
Source notes citing this source
- IP Office Manager's binary .exp export can include record types the CSV export lacks, including ARS, Incoming Call Route, Line, Time Profile, Auto-Attendants, Account Codes, Authorization Codes, User Rights and Location. in context
- IP Office Manager CSV export files use commas as field separators, with no text delimiters and no header row. in context
- IP Office Manager's File > Import/Export CSV export is limited to Groups, Users, Directory, System Short Codes, Licenses (ADI only) and Full Configuration. in context
- IP Office Manager reads and writes CSV files as UTF-8, and Avaya warns that applications such as Excel may use a different encoding that removes or corrupts accented characters. in context
- By default IP Office Manager exports and imports to a subfolder of the Manager application directory named after the loaded system. in context
- Avaya describes the IP Office Full Configuration CSV as too complex to edit by hand and intended only for transferring settings between systems. in context
- In IP Office Manager 12.3 the Group CSV field order is Name, Extension, Group, Hunt, Rotary, Longest Waiting, Queuing On, Voicemail On, Broadcast, Voicemail Email. in context
- IP Office Manager can export licenses to CSV only for ADI licenses. in context
- In IP Office Manager 12.3 the User CSV field order is Name, Extension, User Rights, Email Address, Full Name, Password, VoiceMail Code, Login Code, User Template, Extension Template. in context
- Importing settings into IP Office through Manager overwrites any existing records that match a record being imported. in context
- Because the IP Office CSV export covers only users, groups, directory, system short codes, ADI licences and an opaque full-configuration file, call-routing data a cloud platform must rebuild (incoming call routes, ARS, time profiles, auto-attendants) has to be documented from the Manager configuration or a binary export rather than from editable CSVs. inferred in context
Cite this source record
APA
WarmTransfer. (2023, March 8). Importing and Exporting Settings (Administering Avaya IP Office using Manager 12.3). WarmTransfer. https://warmtransfer.net/knowledge/sources/avaya-docs-ipom123-import-export-settings
BibTeX
@misc{warmtransfer-avaya-docs-ipom123-import-export-settings,
title = {Importing and Exporting Settings (Administering Avaya IP Office using Manager 12.3)},
author = {{WarmTransfer}},
year = {2023},
url = {https://warmtransfer.net/knowledge/sources/avaya-docs-ipom123-import-export-settings},
note = {Avaya LLC, accessed 2026-10-14}
}