Bring your helpdesk with you.
Moving from another platform is the biggest friction point in switching helpdesks. We’ll handle the move so your team doesn’t have to.
Migration is a paid professional service. We scope it to your situation and quote it before you commit.
From wherever you are now.
We’ve migrated installations from a range of platforms:
- Zendesk — clean API export, well-documented schema
- Freshdesk — full ticket history, contacts, and custom fields
- Help Scout — conversations, customer records, tags
- SupportPal — direct database migration possible in many cases
- Zammad — REST API export with attachment retrieval
- Jira Service Management — projects, issues, comments, attachments
- Vanilla osTicket on legacy infrastructure — the simplest case (same database schema)
- Other platforms — most ticketing systems can export structured data; ask us
If your platform isn’t on the list, tell us about it. Where there’s data, there’s usually a path.
From inquiry to live system.
- Tell us about your setup. A short intake covers your source platform, approximate ticket volume, agent count, and what you want to bring across. No passwords. No SSH credentials. No server access. This stage is discovery, not implementation.
- We’ll send you a quote. Most quotes go out within two business days based on your intake answers. For larger or more complex projects (heavy automation, compliance constraints, 10,000+ tickets) we’ll typically suggest a paid migration assessment first, to scope the work properly. The assessment fee credits 100% to your project cost if you proceed.
- If you accept, we coordinate access and execute. This is when credentials become relevant. You provide one-time, scoped access; we encrypt anything you submit at rest, revoke it immediately after migration, and recommend you rotate any passwords you shared.
No credentials at the quote stage.
We don’t need any of these to give you a quote:
- Admin passwords
- SSH or FTP credentials
- Database credentials
- Server access of any kind
Quoting is a conversation, not an audit. For most platforms, a few answers about your environment plus an optional read-only screen-share are enough to scope the work. Credentials, if they’re needed at all, come at the execution stage, and only ever as one-time scoped access that you rotate when we’re done.
Every migration is different. So is every quote.
Migration cost depends on factors that don’t fit a flat fee:
- Source platform. Some have clean APIs (Zendesk, Freshdesk). Some require more invention.
- Ticket volume. A 500-ticket migration is materially different from 100,000 tickets, both in API time and in attachment transfer.
- Time scope. “Last two years” versus “everything ever” can be a 10× effort delta.
- Agent and workflow complexity. Five agents with default settings is a quick remap. Fifty agents with custom views, macros, automations, and SLA targets is a real engagement.
- Custom fields and automations. What maps cleanly, what gets rebuilt, and what gets dropped.
- Attachment volume. Large archives drive transfer time and storage planning.
- Compliance constraints. GDPR, HIPAA, and data residency requirements all affect how the migration is structured.
- Cutover model. A clean weekend cutover is simpler than parallel running with open tickets in flight.
Rate: $150 USD/hour
The same rate as Hire a Pro. Migration projects are quoted in advance for defined scope, with no open-ended billing.
For larger or compliance-bound projects where the intake form alone isn’t enough to scope, we’ll propose a paid migration assessment: a fixed $250 fee, deliverable is a written migration plan with scope, timeline, and risk register. The assessment credits 100% to project cost if you engage us for the migration itself.
Already running vanilla osTicket?
Migrating from vanilla osTicket to osTicket Awesome is the simplest case. Same database schema, same stack, same conventions. Most existing osTicket installations can be moved in a single afternoon with no data loss.
Flat-fee migrations are available for existing osTicket installations. The quote follows the intake form — numbers don’t go on the page because every site has its own custom modifications, plugin states, and branding decisions, but the answer arrives quickly.
Common questions.
What platforms can you migrate from?
The list above covers the common ones. If yours isn’t on it, ask. Most ticketing systems can export structured data, and where there’s data, there’s a migration path.
How long does a typical migration take?
Most projects fall in the 1–3 week window from quote acceptance to live system. Compliance-bound or 100,000+ ticket migrations can run longer. Your quote will include a timeline.
Will I lose any data?
Tickets, comments, attachments, custom fields, and end-user records all migrate cleanly from major platforms. Some things (workflow automations, third-party app states, certain integrations) typically require explicit decisions about what maps, what gets rebuilt, and what gets dropped. We flag these in the quote.
Will my agents need new accounts?
Agent records carry over, but agents will set new passwords on first login. SSO, LDAP, and OAuth2 integrations work on day one if your environment supports them.
Can we run both systems in parallel during cutover?
Yes, in most cases. Parallel running adds complexity to the engagement and we’ll scope it explicitly. Most customers prefer a clean weekend cutover.
Do you handle compliance-bound migrations?
Yes. Healthcare, financial services, and government engagements typically run through the paid assessment so we can scope the data-handling protocols up front. We don’t process PHI or regulated PII without explicit handling agreements.
What if the intake form isn’t a good fit for my situation?
Tell us anyway. Use the description field. We read everything that comes in.
Tell us about your migration.
You’ll hear back within two business days.