Configuration Export

Exporting User and Service Configurations as CSV or JSON

The Export Configuration feature allows Nimbus administrators to export user and service configurations as downloadable files in JSON or CSV format. This supports audits, backups, migrations, and support sharing without requiring technical Nimbus API expertise.

Good to know

The export feature uses the Nimbus API to retrieve details. When triggered, the system: 

  • … iterates over all users or services visible to the logged‑in user. Note that related / referenced entity data may be visible in the export, not just the selected
  • … calls the existing configuration read API per entry.
  • … collects the full configuration payload. 
  • … aggregates the configuration into a single export file.
 

Export Formats

The export supports two formats, selectable via the UI buttons:

Format Content-Type Description
JSON application/octet-stream

Full structured JSON data with nested {"objects"}. Each entry contains tab data from the respective service / user settings. Details are exported as follows…

CSV text/csv

Human-readable flat CSV with one column per field1. Fields are taken from service / user settings respectively.


🔎The CSV format applies the following transformations:

  • Universal quoting: All cell values are wrapped in double quotes for maximum compatibility across Excel locales (handles commas, semicolons, pipes, and other locale-specific delimiters)
  • License normalization: Active / Enabled (Inactive) / Disabled [Reason1; Reason2]
  • Duration formatting: TimeSpan values rendered as 1m, 20s, 10m, 1h 30m
  • Boolean normalization: Yes / No
  • Organization Unit resolution: Organization Unit GUIDs resolved to display names
  • Lists: Skills, Roles, Profiles, Distribution Policies joined with semicolons and space e.g. English; German
  • Missing data: Rendered as None or empty string
  • Friendly role names: Nimbus Portal Role identifiers (e.g. NimbusServiceSupervisor) are converted to space-separated display names (e.g. Nimbus Service Supervisor). Custom Roles names are preserved as-is.

Due to the nature of how Nimbus data entities are nested, some exports will not have the full level of detail (e.g. Nimbus user profiles will be exported, but not the skill levels per user per particular profile).

→ If you require the full details level for each entity, we strongly recommend to use the JSON export instead.

 

Export Procedure

  1. Log into to Nimbus Admin Portal.
  2. Select either Services or Users to get to the overview.
  3. Select one or several service / user entries via their checkboxes in the first column.
    💡You can select entries across multiple pages.

    ⮑ A popup opens, presenting with additional options.
  4. Click on “Export JSON” or “Export CSV”.
    ⮑ An exported text file is being generated and then downloaded by your browser.

 Service Data

Service - JSON Export

Filename pattern: services-config-YYYYMMDD-HHmmss.json
Returns full structured data with nested objects per tab. Suitable for programmatic processing, Power Query import, or archival.

💡Example service export JSON file (collapsed and shortened for readability) 

{
  "exportType": "Services",
  "exportedAt": "2026-04-02T07:04:20.0457135+00:00",
  "totalRequested": 2,
  "totalSucceeded": 2,
  "totalFailed": 0,
  "entries": [
    {
      "id": "91daad4d-1f3c-41a3-b7c7-5baa06349205",
      "displayName": "Documentation Team",
      "general": {
      "profiles": null,
      "skills": null,
      "roles": null,
      "nars": null,
      "assistant": null,
      "interact": null,
      "modalities": {
      "distribution": {
    },
    {
      "id": "86eb9d0e-5068-4e67-a89b-c3d0137ac8c2",
      "displayName": "Documentation Team Skill-based",
      "general": {
      "profiles": null,
      "skills": null,
      "roles": null,
      "nars": null,
      "assistant": null,
      "interact": null,
      "modalities": {
      "distribution": {
    }
  ],
  "errors": [],
  "organizationUnitNames": {}
}

Service - CSV Export

Filename pattern: services-config-YYYYMMDD-HHmmss.csv
Returns a human-readable flat CSV with one column per field. Designed for opening directly in Excel for filtering, sorting, and comparison.

Column Format
Service Name Direct
Service Email Direct
Organisation Unit Resolved to name
PSTN Enabled Yes / No
PSTN Number Direct or empty
Advanced License normalization
Enterprise License normalization
Contact Centre License normalization
Interact (Add-on) License normalization
Acceptance Time Duration format
Hangup Time Duration format
Short Conversation Threshold (s) Integer
Service Call Enabled Yes / No
Teams Channel Direct or None
Mailbox Direct or None
Workflow : Audio/Video Name or None
Workflow : Outbound A/V Name or None
Workflow : IM Name or None
Workflow : Email Name or None
Workflow : External Task Name or None
Workflow : WhatsApp Name or None
Workflow : SMS Name or None
Transfer on Exit Target Name or None
Distribution Policies Semicolon-separated
User Assignment All Users / Policy-Based
Distribution Priority Enum name
ACW Enabled Yes / No
ACW Duration Duration format
ACW Allow Stop Yes / No
ACW Allow Extend Yes / No
Persistent RONA  Yes / No
RONA Reset Time Duration format
Available When Busy Yes / No
Available When Away Yes / No
Default Enability Yes / No
Emergency Redirect Yes / No
Emergency Redirect Destination Direct or empty
Hide User Statistics Yes / No
Show on Historical Page Yes / No
 
 

Exporting User Data

User - JSON Export

Filename pattern: users-config-YYYYMMDD-HHmmss.json
Returns full structured data with nested objects per tab. Suitable for programmatic processing, Power Query import, or archival.

💡Example user export JSON file (collapsed and shortened for readability) 

{
  "exportType": "Users",
  "exportedAt": "2026-04-02T06:27:49.7303885+00:00",
  "totalRequested": 2,
  "totalSucceeded": 2,
  "totalFailed": 0,
  "entries": [
    {
      "id": "344473b3-9250-401f-bce9-72497533118a",
      "displayName": "Ada Lovelace",
      "general": {
      "profiles": {
      "skills": {
      "roles": {
      "nars": {
      "assistant": {
      "interact": {
      "modalities": null,
      "distribution": null
    },
    {
  ],
  "errors": [],
  "organizationUnitNames": {}
}

User - CSV Export

Filename pattern: users-config-YYYYMMDD-HHmmss.csv 
Returns a human-readable flat CSV with one column per field. Designed for opening directly in Excel for filtering, sorting, and comparison.

Column Format
Display Name Direct
First Name Direct
Last Name Direct
Email Direct
Organisation Unit Resolved to name
Contact Centre License normalization
Attendant Console  License normalization
Assistant  License normalization
Instant Messaging License normalization
Email (Licence) License normalization
Audio/Video License normalization
Web Interact  License normalization
External Task License normalization
Companion License normalization
Skills Semicolon-separated; None if empty
Active Profile Single value
All Profiles Name (Default, Active); Name
Roles Friendly Name ( OU ); … semicolon-separated
Task Parallelisation Yes / No
NARs Enabled Yes / No
Interact Enabled Yes / No
Interact AV Yes / No
Interact IM Yes / No
 
 

Table of Contents