Choose Freshdesk scope and mappings
Use a narrow first import to check the mappings and content quality. Scope, mappings and defaults belong to the same organization configuration.
Choose scope
- Open Configuration > Support AI > Freshdesk import > Scope.
- Enable solutions, tickets or both.
- For tickets, set the first creation date and any historical end date. Decide whether later new tickets should be included.
- Discover account values. Choose All explicitly or select categories, folders, ticket statuses, groups, products and tags.
- Choose the source languages. Decide whether to include descendant folders or source article drafts.
An empty Selected filter is invalid. Switching sub-tabs does not turn it into All. Creation dates define the ticket population. Update times find changes within that population.
Review mappings
Open Mappings and discover Freshdesk fields. Review priority and status suggestions. Freshdesk Medium maps to Eos Normal. Review what Pending means for your team before acknowledging it.
Map source groups to queues and source agents to eligible Eos users. Unknown values need review. Map compatible custom fields only to existing supported destination fields. You can also map source folders to existing Eos folders. Those folders keep their names and permissions.
Set defaults
Choose the import root and fallback queue. Decide whether to preserve hierarchy, create missing referenced customers, copy files and include private notes. Published source articles still arrive as staff-only AI-excluded drafts. Ticket history imports without ordinary customer notifications or ticket automation.
Check the result
Save the configuration and inspect a preview. Do not assume that a standard suggestion is correct for a custom Freshdesk workflow. See preview and baseline import.