Migrate from NICE CXone to Freshdesk

CXone Contacts export via ACD API with standard fields (name, phone, email) and all Digital Custom Fields preserved as labeled customer properties in Freshdesk. We map CXone's contact ID as an external_id for dedupe on subsequent delta imports. If the customer uses CXone's Customer object (separate from Contact), we map it to Freshdesk Organization and link it to the Customer record via a custom field.

CXone Agent profiles export with email, name, team assignment, and Skill associations. We map each CXone agent to a Freshdesk Agent record by email match and note the original Skill assignments in a migration comment field. If CXone Skills map to Freshdesk Groups, we perform a pre-migration Group creation in Freshdesk so the Agent-to-Group assignment resolves at insert time. Agent proficiency scores and security group memberships have no Freshdesk equivalent and are excluded.

CXone routing Skills control which agents handle specific interaction types. Freshdesk has no Skills equivalent; routing logic is handled via Group membership and ticket assignment rules. We export CXone Skills as a standalone lookup table, then map each Skill to a Freshdesk Group. If multiple CXone Skills share an agent cohort, those agents join one Freshdesk Group, and the skill-type metadata is preserved in a Group description field for the admin to reference when building Freshdesk automation rules post-migration.

CXone Queues hold interactions and assign them to Skills or Agents. We export queue membership records and map each CXone Queue to a Freshdesk Group, with the queue-level SLA target preserved in a custom field on the Group. Queue priority rules and overflow configurations are documented in the routing rules inventory and do not migrate as code.

CXone Digital Custom Fields (text, email, dropdown) on Contacts and cases export with field definition (ident, label, type) and values. We recreate field definitions in Freshdesk as custom ticket fields or custom customer fields matching the original type and label. The field ident from CXone is preserved in the Freshdesk field description for traceability. Boolean and date field types map directly; dropdown fields require pre-creating the Freshdesk dropdown options before value import.

CXone Address Books manage entity lists and agent assignments. We export address book entries as flat records and map them to Freshdesk Organizations if they represent companies, or to Customer records if they represent individual contacts. Dynamic address book rules (auto-populated based on CXone criteria) are flagged in the routing rules inventory and require manual reconfiguration in Freshdesk.

CXone interaction records (voice calls, chat sessions, emails) export as conversation records via CXone ACD API. We map each interaction to a Freshdesk Ticket with the original channel type (phone, chat, email) preserved in a custom field, timestamp preserved as Freshdesk created_at, and agent assignment resolved via the CXone-to-Freshdesk agent email mapping. CXone disposition codes and wrap-up data map to Freshdesk ticket status transitions and custom status fields.

CXone Knowledge Management articles export via API with article content, category assignments, and status flags (draft, published, archived). We map them to Freshdesk Knowledge Base articles preserving title, body content, and category structure. Folder hierarchy from CXone maps to Freshdesk category folders. Published status migrates as published; draft status migrates as draft for the admin to review before publishing in Freshdesk.

CXone Studio scripts define IVR flows, routing logic, and digital workflows. IVR menus, conditional branches, and queue-to-skill routing have no Freshdesk equivalent because Freshdesk does not include a native IVR or ACD routing engine. We export script metadata (script name, version, active/inactive status) and document every routing decision point in a written inventory for the customer's admin to rebuild using Freshdesk automation rules or the Freshdesk Contact Center IVR if the Omnichannel Suite is purchased.

CXone Workforce Empowerment schedules and exception records (WEM module) export if the customer's license covers WEM. Freshdesk has no agent scheduling or WFM module. We export schedule template names and agent-timezone assignments for the customer's reference but note that schedule rule configuration cannot transfer. Teams needing agent scheduling post-migration should evaluate Freshdesk integrations with third-party WFM tools or consider Freshservice's asset and service management capabilities as a separate engagement.