Migrate your TOPdesk data

Calls are the core ticket object in TOPdesk, covering both incidents and service requests. They support custom fields, statuses, priorities, and operator assignment. We map Calls 1:1 to the destination ticket object and preserve the full activity/communication thread.

TOPdesk distinguishes Simple Changes (status=2), Extensive Changes (status=3), and Requests for Change (status=1, phase 2). Each change can have authorization activities, versions, milestones, and meetings attached. We preserve the full change lifecycle including any linked activity templates.

Assets in TOPdesk have a rich hierarchy: each asset can link to other assets, people, locations, and financial data. Status codes (1=active, 2=item) affect which API endpoint is used. We map the full asset tree, including parent-child relationships and custom fields on each asset class.

Configuration Management items in TOPdesk store IT infrastructure components. The API endpoint is 'configuration' and maps to the Configuration object. Custom fields and linking behaviour require field-level mapping because CI schemas vary significantly between organisations.

Operations Management Series group activities into a structured process schema. Series in preparation (status=1) and activated series (status=2) behave differently in the API. Schemas aggregate related series. These objects are specific to the OM module and require module-availability confirmation before migration.

Known Error Cards store a problem cause and a possible solution. They are first-class objects with their own card type. We preserve the linked problem and the associated workaround text during migration.

People records hold requester information; Operators are the agents who handle calls. Both objects support custom fields and can be linked to assets and departments. We map person records to the destination contact or user object and preserve operator-group assignments.

TOPdesk allows up to five freely definable object types that organisations use for custom entities. These objects have their own schema and custom fields. We handle them as custom objects and map their relationships individually during scoping.

Reservations in TOPdesk track bookings of equipment, rooms, or other lendable assets. The reservation schema is tied to the asset module and may include date ranges, requesters, and status. Availability during migration depends on whether the destination platform has a comparable reservation object.

Attachments can be linked to calls, changes, assets, and other objects. We extract attachment metadata (filename, size, content type) and the binary where accessible via the API, mapping each attachment to the corresponding destination record.

TOPdesk supports text fields, date/time fields, checkboxes, number fields, currency fields, and drop-down lists. Custom fields added by administrators are included in our migration scope but require field-level mapping because field IDs and data types differ between source and destination instances.

TOPdesk automates operator workflows using events and actions. Activity templates define reusable process steps for changes and other objects. We extract workflow configuration as structured metadata; full workflow recreation depends on the destination platform's automation engine capabilities.