Skip to content
ChaosDesk Support

Import from Salesforce, ServiceNow, Zammad, Kayako, LiveAgent or osTicket

Updated Nov 9, 2026

This feature is in beta: it is still being built and may change.

These sources use the same import page and steps as every other source: connect, estimate, dry run, full import. The import only reads from the old system.

The steps

  1. Open Admin Center, Integrations, Import and pick the source.
  2. Fill in the connection details below, choose Save, then Test connection.
  3. Choose Estimate volume, run a Dry run and read its report.
  4. Run the Full import.
  5. Check the counts with Reconcile: the number of records in the source next to the number in ChaosDesk.

Salesforce Service Cloud

You need:

  • your My Domain address, for example yourcompany.my.salesforce.com;
  • a connected app with the api OAuth scope and the client credentials flow turned on. Enter its consumer key and secret;
  • a run-as user for that app who can view all users, accounts, contacts, cases, case comments and email messages (a system administrator, or a profile with "View All Data").

What comes over: queues (as groups), users (as agents), accounts (as organizations), contacts, and cases with their emails and case comments. The case number is kept.

Rebuild by hand: assignment and escalation rules, entitlements, milestones and flows. For Salesforce Knowledge, import the public knowledge base pages.

Salesforce counts API calls per 24 hours by edition and licences. Each page of a query is one call, so check your allowance before a full import.

ServiceNow

You need: your instance name (the part before .service-now.com), and the user name and password of an integration user. A "web service access only" user is best, with the roles itil and snc_read_only or table ACLs of your own. It must be able to read incident, sys_user, sys_user_group, sys_user_grmember, core_company and sys_journal_field.

What comes over: active assignment groups (as groups), users (members of an assignment group become agents, everyone else end users), companies, and incidents with their comments (public) and work notes (private).

Not imported: business rules, assignment rules, SLAs, workflows, and other task tables such as requests, problems and changes.

Zammad

You need: your Zammad address, starting with https:// (hosted or self-hosted), and an access token (Avatar, Profile, Token Access) of an admin. Give the token the permissions admin.user, admin.group, admin.organization and ticket.agent, with read access to every group.

What comes over: groups, organizations, users (with their Admin, Agent or customer role), and tickets with their articles, tags and attachments. Automatic system messages are left out.

Rebuild by hand: triggers, schedulers, SLAs and macros.

Kayako

You need: your Kayako subdomain (cloud Kayako), and the email and password of an admin. Kayako has no API keys, so create a dedicated admin account without two-factor sign-in for the import and remove it afterwards.

What comes over: teams (as groups), organizations, users (owners and admins become admins), and cases with their messages, notes and attachments.

Rebuild by hand: triggers, monitors, SLAs and macros.

LiveAgent

You need: your LiveAgent account (the part before .ladesk.com, or your own domain) and an API v3 key with read access (Configuration, System, API).

What comes over: departments (as groups), agents, companies, contacts, and tickets with their messages and internal notes.

Not imported: rules, SLA levels, canned messages, and file attachments of messages.

osTicket

osTicket has no API to read tickets, so you export the data on your osTicket server and upload the file.

  1. Download the osTicket export script. It only reads your osTicket database and is tested against the osTicket 1.14 to 1.18 schema. The server needs PHP with pdo_mysql.
  2. Copy it into your osTicket folder, next to the include folder.
  3. On the server, run php osticket-export.php > osticket.json. From another folder, point it at the config: --config=path/to/include/ost-config.php.
  4. In ChaosDesk, pick osTicket on the import page and upload osticket.json (at most 20 MB).
  5. Check the counts it shows, then run a Dry run or the Import.

What comes over: departments (as groups), staff (as agents), organizations, users, and tickets with their messages, responses and internal notes. Ticket numbers are kept.

Not exported: filters, SLA plans, canned responses, help topics and attachments. osTicket has no delta sync, so to bring later changes over you upload a newer export. Unchanged records are skipped and nothing is duplicated.

Help centres

None of these sources imports a knowledge base through the API. If yours is public, import it from its website.

Salesforce, ServiceNow, Zammad, Kayako, LiveAgent and osTicket are trademarks of their owners. ChaosDesk is not affiliated with them.

Related

Was this article helpful?

Still need help?

Submit a request
Import from Salesforce, ServiceNow, Zammad, Kayako, LiveAgent or osTicket · Help Centre