TOPdesk — Migration Reference – Relokia

TOPdesk — Migration Support Overview

Role in migrations

Staff (HD): supported as source.
Company (HD): supported as source.
Contact (HD): supported as source.
Ticket (HD): supported as source.
Change (HD): supported as source.
Category (KB): supported as source.
Folder (KB): supported as source.
Article (KB): supported as source.

Field-level support migrating FROM TOPdesk (Ticket)

Field	Supported
Requester	Yes
Company	Yes
Assignee	Yes
Group	Yes
Attachments	Yes
Comments	Yes
Tags	Yes
Custom fields	No
CC	No such field in platform
First Response Time	No
Created date	Yes
Updated date	Yes
Closed date	Yes

Field-level support migrating FROM TOPdesk (Company)

Field	Supported
Domains	No such field in platform
Tags	No such field in platform
Custom fields	No such field in platform
Notes	No such field in platform

Field-level support migrating FROM TOPdesk (Contact)

Field	Supported
Tags	No such field in platform
Custom fields	No such field in platform
Phone	No
Notes	No

Field-level support migrating FROM TOPdesk (Article)

Field	Supported
Inline images	Yes
Attachments	No
Tags	No
Support multilevel Folder structure	No

Field-level support migrating FROM TOPdesk (Change)

Field	Supported
Requester	Yes
Company	No
Assignee	Yes
Group	Yes
Attachments	Yes
Comments	Yes
Tags	No such field in platform
Custom fields	No such field in platform
Created date	Yes
Updated date	Yes
Due date	No such field in platform
Closed date	No such field in platform
Planned start date	No such field in platform
Planned end date	No such field in platform
Task	No such field in platform
Task notes	No such field in platform
Task attachments	No such field in platform

Migration options available for TOPdesk

Migrate the newest records first - applies to: source (Ticket), source (Change)
Select records for Demo- applies to: source (Ticket)
Inline images in tickets - applies to: source (Ticket)
Skip ticket attachments - applies to: source (Ticket)

TOPdesk — Setup & How-To Guide

For more information: https://help-desk-migration.com/help/topdesk-migration-guides/

How to create an application password for API

To use the API, an application password is required instead of the web interface login password. This setup is currently available only for operators.

Create an application password:

Go to Operator menu > My Settings in the top right of TOPdesk. In the Application passwords block, choose 'Add'.
In the "Create a new application password" popup, enter the application name or purpose. This helps differentiate between passwords for different applications using the API. Optionally, set an expiry date for the password. The default expiry is one year.
Click the "Create" button. The password will be displayed in the "Copy the application password now" popup.

TOPdesk migration limitations

Subcategory and Category fields are merged into a single field on articles mapping
Older on-premise versions lack the API module, which means data cannot be read via API. If a client is on an unsupported version, there are two options:
1. Upgrade the Topdesk version (note: there is a risk of data loss in Topdesk during the upgrade).
2. Export a database dump, from which a custom migration can be performed.

Search

TOPdesk — Migration Reference