I've Paid the Migration Tax
I've been on both sides of this. As a support lead, I once spent three weeks migrating ticket history between platforms -- mapping fields in spreadsheets, writing throwaway Python scripts, re-importing the same CSV eleven times because one column kept breaking. And then I watched competitors charge thousands of dollars just to let customers take their own data somewhere else. Your data, held hostage behind a migration fee.
Both experiences made me angry. The quiet kind. The kind that turns into a product feature.
Zendesk charges up to $100,000 for enterprise migrations. Help Desk Migration starts at $100 for 1,000 records and climbs to $4,200 for their premium package. Freshdesk can't even import tickets via CSV. Front limits you to 3,000 records per import. HubSpot users -- and I'm paraphrasing dozens of forum posts here -- basically say don't even attempt CSVs.
83% of data migration projects fail or go over budget. That's not a technology problem. That's a priorities problem. The incumbents have zero incentive to make leaving easy.
So we built the importer we wished existed.
The Universal Importer
One wizard. Upload your export file. cStar figures out the rest.
Auto-detects your platform. Zendesk JSON export, Freshdesk CSV, Intercom dump, whatever you've got. cStar reads the file structure and tells you what it found. No configuration screens. No twenty-question setup flow.
Maps your fields automatically. Customer Email maps to email. Ticket Subject maps to title. The importer reads column names, makes smart suggestions, and gets out of your way. Most of the time, the defaults are right. When they're not, you adjust. Two clicks.
Handles tickets, customers, and articles. Not just contacts. Full ticket history with conversations. Customer profiles with metadata. Knowledge base articles with categories. Everything you need to hit the ground running -- no warp zone required, but it feels like finding one.
Preserves your timestamps. This matters more than people think. SLA metrics, response time history, analytics -- all of it stays accurate because we keep the original dates. Your historical data doesn't reset to "imported on March 30th." That would be useless.
Smart merge, not blind overwrite. Already have records in cStar? The importer matches by email, ID, or any field you choose. Per-field merge strategies: Update if empty. Always overwrite. Never touch. Append. You control what changes and what doesn't.
Nine Platforms, Zero Configuration
Built-in mappers for Zendesk, Freshdesk, Intercom, Help Scout, HubSpot, Front, Crisp, LiveAgent, and Zoho Desk. Plus generic CSV, JSON, and XLSX support for everything else. If your data exists in a file, we can probably eat it.
Preview Before Anything Touches the Database
The importer shows you exactly what will happen before a single record is written. New records. Matched records with a full diff. Skipped records. You see the future before you commit to it -- 1.21 gigawatts of confidence.
For matched records, you pick the merge strategy per field. Always update. Update if empty. Never update. Append. No surprises.
Seven Steps, Most of Them Automatic
- Upload -- Drag and drop. CSV, JSON, XLSX, up to 50MB.
- Detect -- Platform and entity type identified automatically.
- Map Fields -- Auto-mapped. Adjust if needed.
- Match and Merge -- Handle existing records your way.
- Preview -- See creates, updates, skips before they happen.
- Execute -- Real-time progress.
- Summary -- Results and error reports.
Most people spend their time on step 5, nodding and clicking "go."
Large Migrations
The importer handles up to 10,000 records per file. Got 50,000 customers or 200,000 tickets? Split your export into chunks.
The key: saved configurations. Map your fields once on the first import. Save the config. Load it for every subsequent file. Each import after the first takes a couple minutes because you skip straight to preview.
50,000 records becomes 5 imports. 200,000 records becomes 20 imports. A bit of elbow grease? Sure. But compare that to paying a consultant thousands of dollars or spending weeks writing API scripts that'll never run again.
Save your field mappings, merge strategies, and match settings. One click to re-run. This turns the importer from a migration tool into a maintenance tool -- update customer tags from a spreadsheet, sync ticket data monthly, fix a batch of wrong priorities from a quick CSV. The importer sticks around after migration day.
What It Costs
Nothing extra. The Universal Importer is included with every cStar seat. No migration fee. No professional services charge. No "contact our migration team" upsell.
Zendesk: $8,000-$100,000 migration services. Help Desk Migration: $1,080-$4,200 packages. Freelance developer: $2,000-$15,000 and a prayer.
cStar: included.
We built this because your data should move freely. Trapping it behind expensive migration barriers isn't a feature. It's a hostage situation dressed in enterprise clothing.
Try It
The importer lives in Settings > Team Tab > Import Data. Upload a file and see what happens.
Your data. Your choice. Allons-y.
Written by Josh Lopez. He has personally imported the same test CSV so many times that the sample customers feel like old friends.