Why the community thread happened
Moving the records is easy. The confusion comes afterwards: thousands of customers exist in Zendesk with no password, and they get an email they didn’t expect, or no email at all. Decide how people will sign in before you import.
Steps
- Export Freshdesk contacts and companies with email, name, phone, company and custom fields. Keep the Freshdesk contact ID.
- Import organizations first (Freshdesk companies), so users can be linked to them.
- Decide the email behaviour.
- Admin Center > People > Configuration > End users has the checkbox “Also send a verification email when a new user is created by an agent or administrator”.
- Add a
skip_verify_emailcolumn set totrueto create users without the verification email. - Note that “when Guide is enabled, each user receives the welcome email message.”
- Import users with the data importer (up to 1 GB, 200 columns and 128 KB per row; recommended maximum 500,000 rows). Put the Freshdesk ID in a user field.
- Import tickets afterwards, through the Ticket Import API, with requester IDs resolved to the new users.
- Tell customers how to sign in: a branded “set your password” email at go-live, or SSO.
What the native tool does / where it stops
| Need | Zendesk native | Gap |
|---|---|---|
| Create users in bulk | Data importer (CSV) | Organizations must be loaded or matched separately |
| Control emails | Verification setting plus skip_verify_email | Welcome email behaviour depends on whether Guide is on |
| Passwords | None | Users must set or reset one, or use SSO |
| Agents | Created separately with roles | Assignment mapping is manual |
| Ticket history | Ticket Import API, or the Freshdesk Migration app | No CSV ticket import in the UI |
What the docs don’t spell out is the sign-in path for suppressed users. If you skip verification and don’t use SSO, users can only get in through “Forgot password”. Put that in the cutover email.
Where FlitStack AI fits
FlitStack AI migrates Freshdesk contacts, companies and agents (matched by email), then tickets with threads and attachments. A legacy ID is kept for cross-reference. See Freshdesk to Zendesk or the Zendesk migration page.