1. Don't reset or revoke the API key you submitted. Resetting it in Freshdesk (Profile Settings) revokes the old key and disconnects Zwitch mid-migration.
   
2. Disable any Zoho CRM or Salesforce integration during migration to avoid duplicate contacts and accounts.
   
3. Remove any IP restriction settings that could block access.
   

What happens during data processing?

1. Data format: Freshdesk data is accepted in XML and JSON format.
2. Zoho Desk migration:
1. Zoho Desk has a migration wizard with a template for Freshdesk data.
2. Use Zwitch to submit a Freshdesk backup for validation.
3. The wizard extracts data module-wise and makes API calls to Freshdesk.
3. File naming: Keep backup file names unchanged as exported from Freshdesk.
4. Data deletion:
1. Freshdesk backup files processed by the wizard are periodically deleted.
2. Records are purged within 30 days of confirmation of migration.
5. Freshdesk account maintenance:
1. Keep Freshdesk account active until the final migration.
2. Maintain the account with sufficient API rate limits for access during migration. The migration might take a minimum of two weeks, so ensure that the request is raised well within the subscription period. 

Note:

1. All Freshdesk requesters/contacts arrive as EndUsers in Zoho Desk. If you don't want this, leave the EndUsers module out of the submission.
2. Selecting Tickets automatically includes Threads, Ticket Comments, and Attachments.
3. Deleted contacts are not included in the FreshDesk backup files. Hence tickets associated to the deleted contacts will not be migrated.
4. Zwitch migrates everything into a single department (the default, or one you choose). Splitting data across multiple departments in one pass is not supported.
5. A migration can be cancelled only while its status is "Submitted in Queue." Once it starts processing, it can't be cancelled.

Data migration rule

1. Ticket identification:
   
1. Tickets can be filtered with Freshdesk groups and products. Users can also skip irrelevant tickets and only migrate the selected ones into Desk.
   
2. Freshdesk ticket IDs are preserved in the field 'display-id'.
2. Custom fields in Desk:
1. Desk custom field names may vary slightly, but types and values remain unchanged.
2. Custom fields are created dynamically during migration, with types predicted from sampled data.
3. Custom fields are subject to subscription-based limits and predefined regex pattern checks.
3. Ticket notes and threads:
1. Freshdesk ticket notes become Threads and Comments based on their privacy flag. Private notes turn into ticket comments, while public ones become threads.
4. Channel tagging:
1. Threads with an email address are mapped to the Email channel. If no channel or email address is available, the thread is mapped to the 'CUSTOMERPORTAL' channel.
   

Key facts at a glance  

1. Sign in to Freshdesk account.
2. Click Admin icon (  ) on the left panel > Account > Account Details.
   
   
3. On Account Details window, hover to Export data and click Export.
   
   
4. Click on Any time, select a time range for created 
1. Tickets
2. Contacts 
3. Companies
   
4. Solutions, to be transferred. 
   
   
   
5. Click Update.
6. Click Export.

To check the export status

1. Once Export has been initiated, a popup appears with the following message. 
   You will be directed to Account exports page.
   
   
   
2. Alternatively, Click Admin icon (  ) on the left panel > Account > Account Exports.
   
   
3. To check the details of exported files, click Details.
   
   
4. Click Download.

Note: Read more on how to import data from Freshdesk to Zoho Desk.

Also See 
1) Migrate Data From Other Help Desk Servers to Zoho Desk (Zwitch).
2) FAQs about Zwitch