Migrate your Teamwork Desk data

Customers are the primary contact object in Teamwork Desk. We migrate customer records including name, email, company, and metadata. Spam-marked customers are excluded from Teamwork's native export, which we replicate to avoid polluting the destination.

Tickets are the core help desk object in Teamwork Desk, with support for statuses, priorities, assignees, tags, and thread-based replies. We preserve full conversation history including internal notes. Custom fields on Premium and Enterprise tiers require field-level mapping.

Agents represent support staff in Teamwork Desk. We map agent records including role, inbox assignment, and active/inactive status. Owner assignment on tickets is preserved by mapping to the corresponding agent record in the destination.

Inboxes in Teamwork Desk route incoming tickets from specific channels (email addresses, forwarding rules) to designated agents. We preserve inbox-to-agent assignments so routing logic carries over to the destination.

Categories are used to organize Helpdocs articles. They have a hierarchical structure that may not map directly to every destination's category or folder model. We preserve the hierarchy as tags or a flat category list depending on the destination's support.

Helpdocs are the knowledge base articles customers can reference before submitting tickets. We export articles including content, category associations, and publication status. Article attachments are handled as file references that we re-attach at the destination.

Tags in Teamwork Desk are used to label tickets and customers for filtering and reporting. We migrate tags as-is and recreate the tag vocabulary in the destination, mapping them to any native tagging system available.

Custom fields are only available on Premium and Enterprise tiers. They can be dropdown, text, date, or number fields applied to tickets or customers. We flag every custom field during scoping and map values to equivalent custom fields in the destination or store them as custom properties.

Time tracking in Teamwork Desk logs billable or non-billable time against tickets. Not all destinations support time-log migration. We export time entries as a separate line-item export and either create time records in the destination or attach them as ticket comments.

Business Hours define when the support team is available for SLA calculations. This is a Teamwork Desk configuration object with no data payload to migrate. We recreate it in the destination settings manually during setup.

CSAT ratings attached to tickets are migrated as a custom numeric or rating field in the destination, since not all platforms store customer satisfaction scores natively on ticket records.

Reports and analytics are not data records but generated views of tickets, agents, and SLA metrics over time. We do not migrate reports directly; we recommend rebuilding them in the destination using migrated data.

Triggers are automated workflow rules that fire on ticket events. Migrating them requires translation to the destination's automation engine. We document trigger logic during scoping and implement equivalent rules in the destination as a separate configuration step.

File attachments on tickets and Helpdocs articles are referenced by URL in Teamwork's API. We download attachments and re-upload them to the destination storage, handling size limits and file-type restrictions on both platforms.