Migrate from ProProfs Help Desk to Freshdesk

ProProfs tickets map directly to Freshdesk tickets. Ticket status (open, pending, resolved, closed) maps to Freshdesk status values (open, pending, resolved, closed). Priority from ProProfs maps to Freshdesk priority (urgent, high, medium, low). We preserve the original ProProfs ticket ID as a custom field for cross-reference during reconciliation.

ProProfs customer records map to Freshdesk contacts. Email, name, phone, and company association transfer directly. ProProfs company associations map to Freshdesk company records, which we create first so that the contact-company relationship is satisfied at insert time. Customer ticket history is preserved as Freshdesk ticket associations.

ProProfs company records map to Freshdesk company records. Company name and domain map to Freshdesk company_name and domains fields. We resolve duplicate companies by domain before insert to avoid duplicate Freshdesk company records for the same organizational entity.

ProProfs public conversation messages map to Freshdesk conversation records with type = incoming (customer) or outgoing (agent). We preserve sender type, timestamp, and message body. Conversation threading is maintained by ordering messages against the Freshdesk ticket's conversation list in chronological sequence.

ProProfs private agent notes migrate as Freshdesk internal notes attached to the same ticket. Freshdesk internal notes are visible only to agents, matching ProProfs's private note visibility model. We flag any private notes that reference unresolved ProProfs user IDs that may not have a Freshdesk agent equivalent.

ProProfs agent profiles (name, email, role) map to Freshdesk agent records. ProProfs admin maps to Freshdesk admin; ProProfs agent maps to Freshdesk agent. Team assignments from ProProfs map to Freshdesk groups and team structures. Any ProProfs agent without a corresponding Freshdesk user is held in a reconciliation queue for the customer's admin to provision before the agent migration phase.

ProProfs labels migrate as Freshdesk tags attached to the corresponding ticket. We preserve the label-to-ticket association at the record level. Freshdesk's tag model supports comma-separated tags per ticket, matching the label semantics from ProProfs. Tag counts are reconciled after migration to verify all label associations transferred.

Five of ProProfs's seven custom field types map directly to Freshdesk equivalent field types. Text fields migrate as Freshdesk text fields; number fields migrate as number fields; dropdown fields migrate as dropdown fields with values preserved; date fields migrate as date fields; checkbox fields migrate as boolean fields. We validate field content against Freshdesk schema before import and flag any values that exceed destination field constraints.

ProProfs multi-select fields store values as comma-separated strings. Freshdesk does not have a native multi-select field type. We either store the comma-separated value in a Freshdesk paragraph field with original delimiters preserved, or we split into multiple single-select records if the customer chooses a Freshdesk app extension. The customer selects the strategy during scoping.

ProProfs user reference fields store agent assignments in custom fields. Freshdesk does not have a native user reference custom field type. We either store the referenced agent's email as a text field, or we recommend a Freshdesk Marketplace app for agent lookup fields. The customer selects the approach during scoping based on whether the field is used for filtering or reporting.

ProProfs knowledge base articles from JSON or XML page-level export map to Freshdesk articles with title, content (HTML), author, and section/category. We request page-level JSON or XML exports from ProProfs support or UI as the primary migration source. If the customer only has a PDF full-site backup, we flag this as a high-severity gotcha because PDF requires content reconstruction before import. Article URLs are preserved in a custom field for redirect mapping.