Migrate from Help Desk Premier to Freshdesk

Help Desk Premier Tickets map to Freshdesk Tickets preserving status, priority, assignee (via agent email lookup), requester, and timestamps. Custom Ticket Fields require a field-level mapping pass: text fields map to Freshdesk single-line or multi-line text depending on length; picklist fields map to Freshdesk dropdown; boolean fields map to checkbox. Custom ticket fields are only available in Freshdesk Growth plan and above ($19/agent/month). We flag any unsupported custom field types and route them to the closest Freshdesk equivalent, documenting the discrepancy for the customer's admin.

Help Desk Premier Customer records map to Freshdesk Contacts. We deduplicate by email address, merge duplicate contacts detected during the schema scan, and map the flat contact schema or the separate contact-plus-organization model depending on Help Desk Premier's edition. Contact name, email, phone, and any standard fields map directly. Custom contact fields map to Freshdesk contact custom fields of equivalent type.

Help Desk Premier Company or organization records map to Freshdesk Organizations where they exist. Company name, domain, and any custom company-level fields migrate directly. In editions where Companies are not present, we skip this object entirely. Freshdesk Organizations provide a parent lookup for Contacts, and we resolve the Organization reference before inserting Contacts to avoid orphaned contact records.

Help Desk Premier Agent records map to Freshdesk Agents. We preserve display name, email, role, and group membership. Agent email is the dedupe key during import; if a Freshdesk Agent with the same email already exists, we map to that record. Role terminology varies by Help Desk Premier edition, so we read the role schema during the export scan and map to the closest Freshdesk Role configuration. Inactive or deleted agents from the source are held for the customer to decide whether to create them as inactive Freshdesk agents or reassign their tickets.

Help Desk Premier Team or Group records map to Freshdesk Groups. Team names and memberships migrate directly. Some Help Desk Premier editions restrict team membership to one agent; Freshdesk Groups allow multiple agents. We flag restricted team structures during the schema scan and document them in the migration report so the customer's admin can adjust group membership in Freshdesk post-migration.

Tag vocabularies vary in length and character composition across Help Desk Premier. Freshdesk preserves tag names but strips certain special characters at the platform level. We normalize tag names during the mapping pass, preserving the original tag string where possible and flagging any tag that loses characters due to Freshdesk's validation rules. The normalization pass ensures tags remain searchable in Freshdesk's tag-based filtering.

Help Desk Premier Knowledge Base Articles and KB categories migrate as Freshdesk Folders and Articles with a parent-child relationship preserved. Article body content, category hierarchy, and publication status migrate directly. Article associations to specific tickets do not have a native Freshdesk equivalent and are documented in the migration report rather than migrated. Tags on articles migrate to Freshdesk article tags. We do not migrate KB Redirects as there is no dedicated Freshdesk endpoint for article redirect configuration; we document each redirect URL pair for manual setup in Freshdesk Admin.

Help Desk Premier Conversation records on Tickets migrate as Freshdesk Conversation entries (Reply or Note depending on visibility). We preserve the author (resolved via agent email mapping), timestamp, body content, and visibility flag. If the body contains the less-than symbol followed by !, -, or alphabetic characters, we apply a regex preservation pass before inserting into Freshdesk because Help Desk Premier's export removes these characters while Freshdesk preserves them natively. Inline images migrate as separate attachments linked to the conversation.