Migrate your Trouble Ticket Express data

Tickets are the core object; each carries a unique ID, status, owner, department, and creation date. We migrate all standard ticket fields across all three database backends (plain text, MySQL, SQL Server). All messages, thread history, and inline attachments come with the ticket.

Messages are embedded within tickets and represent the chronological thread between customer and operator. We preserve author, timestamp, body text, and any inline attachments per message.

Customers are email-addressed submitters captured on ticket submission forms. We extract the user database alongside tickets and map it to the destination's contact or requester object. Plain-text editions store customers as a flat file; MySQL/SQL editions use structured tables.

Operators are service desk staff with ticket ownership and assignment capabilities. We export operator records and map them to destination agents or users, preserving department assignments where present.

Custom fields are declared by prefixing form input names with 'x-'. Without Layout Designer they appear only in message bodies as text; with Layout Designer they live in the database and are searchable. We parse both locations and attempt structured mapping to destination custom fields.

File attachments are stored on the filesystem and referenced in the backup module output. We extract them from the backup archive and re-associate them with the correct ticket and message in the destination system.

Tickets and operators carry department assignments. We extract department names and map them to destination team or group structures, noting that small plain-text editions may not have a formal departments table.

The Answer Library is a knowledge-base-like add-on module containing pre-written responses. We extract entries and map them to the destination KB or canned-response structure, flagging that this is an optional module and may not be present in all installations.

An optional add-on that tracks inventory items associated with tickets. We extract this as a supplementary object and map it to the destination's custom object or asset tracker, noting it is only present if the module is purchased.

The backup module exports configuration variables but excludes server-specific paths and the admin password. We parse these to understand workflow rules, email settings, and field labels that may inform field mapping decisions.

The log file is required for reporting within TTX but contains operational audit entries rather than customer data. We do not migrate it as it has no analogue in standard help desk destinations and its format is not documented for reliable transformation.

The base TTX edition does not have a separate tagging object. Tickets carry status and department only. If Labels or Tags exist as a custom add-on in a specific installation, we handle them as a custom-field mapping exercise rather than a standard object migration.