You're leaving Freshdesk. Maybe the pricing scaled too fast. Maybe support got slower. Maybe you need features Freshdesk just won't build. Whatever the reason, you're about to discover that exporting your support history is not the same as actually having it portable. Freshdesk's API is powerful, but it's not designed for bulk export. The standard export function omits conversation history. Full ticket threads require piecing together data from multiple API endpoints. If you have 5,000 tickets, you're looking at thousands of individual API calls—which take time, cost rate-limit errors, and often leave gaps. Here's what actually happens when you leave Freshdesk, where your data goes, and how long it actually takes. What Freshdesk's Standard Export Actually Includes (and Skips) Freshdesk gives you a CSV export. It contains: Ticket ID, subject, status, priority Contact name, email Created date, updated date, resolved date Custom fields (if you mapped them during export) Tags What's missing: Full conversation history — replies, internal notes, attachments Agent assignments — who owned the ticket when SLA data — when you breached, how you recovered Time tracking — billable hours logged against tickets Satisfaction ratings — CSAT responses Automation audit trail — which automations fired, when The standard CSV export is a skeleton. It tells you a ticket existed. It doesn't tell you what happened inside it. If you need the full picture—which you do if you're migrating to stay compliant, keep historical context, or audit support quality—you have to use the API. The API Export Path: Cost and Timeline Reality Freshdesk has a REST API. You can request conversations, notes, contacts, and automations individually. For a 5,000-ticket account with an average of 3 replies per ticket, you're making roughly 15,000 API calls. Freshdesk's free tier allows 50 API calls per minute. Paid tiers top out at 600 calls per minute. At 50 calls/minute, 15,000 calls takes 300 minutes—five hours of continuous API work, assuming zero failures. One network hiccup, one rate-limit timeout, one API maintenance window and you're starting sections of the export over. Timeline for a 5,000-ticket account: Manual API scripting and testing: 8–16 hours Initial export run: 5–8 hours Fixing data gaps and retry logic: 4–8 hours Validation and reconciliation: 4–6 hours Total: 21–38 hours of engineering time, or $2,000–$5,000 in contractor cost Smaller accounts (under 1,000 tickets) can do this in 8–12 hours. Larger accounts (20,000+ tickets) often need two weeks because you hit rate limits, need to batch the work, and inevitably discover data quality issues mid-export. Where Data Actually Gets Lost in Migration Even with a complete API export, three common losses happen: 1. Conversation context collapses Freshdesk stores ticket replies as separate objects. The API returns them as an array. Most migration tools flatten this into a single text field or separate records. You lose the threading—which customer message prompted which agent response, when a note was internal vs. visible to the customer. Zendesk and Intercom preserve conversation threading natively. Chatwoot and Zulip can map it if you export the structure correctly. Most generic helpdesk platforms cannot. 2. Custom fields don't map automatically You have custom fields in Freshdesk. The target platform has custom fields too, but they're named differently, typed differently, or don't exist. A 'Priority Level' in Freshdesk might be a 'Severity' in Zendesk with different value ranges. Without manual field mapping, your data arrives blank or wrong. 3. Agent history gets orphaned If agents have left your company, their Freshdesk accounts are closed or deactivated. The API still returns their IDs in the ticket data, but the target platform can't match them to anyone. Your migration shows 'Agent ID: 4521' instead of 'John Smith', making historical ticket assignment unreadable. Comparing Actual Migration Paths: Zendesk vs. Intercom vs. Self-Hosted Zendesk Data portability: Good. Zendesk has a native Freshdesk importer that handles contacts, tickets, and basic conversation history. They charge $2,000–$5,000 for professional import services, depending on account size. What works: Conversation threading is preserved. Agent assignments map correctly if your Zendesk team structure matches. Custom fields mostly survive. What breaks: Automation history is lost (Zendesk doesn't import it). Time-tracking data is dropped. CSAT scores come across as plain numbers without historical context. Timeline: 2–4 weeks with Zendesk's import team handling the work. DIY import takes 40–60 hours of engineering. Intercom Data portability: Moderate. Intercom's API supports bulk import, but there's no native Freshdesk migration tool. You're building the connector yourself or paying a middleware vendor ($3,000–$8,000). What works: Conversation history imports cleanly. Contact data is straightforward. Intercom's platform is design