Migrate your eTicket data
A lightweight helpdesk ticketing platform for small support teams. Migration data is scarce — scoping calls are critical before any transfer begins.
In its favor
Why people choose eTicket
The signal that keeps eTicket on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
eTicket is free and open-source — the community version has always been free, which makes it attractive to hobbyists, small shops, and educational projects with zero software budget.
PHP-based with simple pop3/pipe email ingestion and web-form ticket creation, making it easy to install on shared hosting that already runs PHP+MySQL.
Self-hosted by design — teams retain full ownership of ticket data and database, which appeals to organizations uncomfortable sending support data to SaaS vendors.
Skinnable to match an existing website's look-and-feel, allowing small businesses to embed a support form that does not look third-party.
Multi-lingual support, CAPTCHA, and configurable spam filtering are included in the core distribution without paid add-ons.
The project is effectively dormant — the latest documented release (1.7.3) is from October 2008, with no modern development cadence, leaving customers exposed to unpatched dependency and security issues.
No public API and no modern integration story — teams that want to connect helpdesk data to CRM, BI, or modern automation tools have no native path.
PHP and MySQL stack assumptions are dated; deploying on modern hosting often requires patching PHP compatibility issues that the upstream project does not address.
Limited reporting and analytics — eTicket is a basic queue-and-conversation tool, with no SLA timers, no advanced workflow, and no dashboard depth that modern helpdesks ship by default.
Migration paths to modern helpdesks (Zendesk, Freshdesk, Help Scout) are entirely manual — there is no published export tool or supported migration partner, so teams must scrape the MySQL database directly.
Reasons to switch
Why people leave eTicket
The recurring reasons buyers give for replacing eTicket. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where eTicket fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
eTicket pricing overview
eTicket's community version is free and open-source, distributed as PHP/MySQL source code under a permissive license. There is no commercial subscription or hosted SaaS tier actively maintained by the original project. Total cost of ownership is dominated by self-hosting infrastructure, PHP/MySQL upkeep, and any custom development needed to keep the legacy codebase running on modern stacks.
Community (free)
Tier 1 of 1
Free — open-source
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on eTicket's schedule — see our quote-based pricing →
What gets migrated
eTicket object support
Object-by-object support for eTicket migrations. Per-pair details surface during scoping.
Tickets
Mapping requiredTickets are the primary object — created via email ingestion (pop3/pipe) or web form. We extract tickets from the eTicket MySQL database, preserving ticket ID, subject, status, priority, and assigned agent. Status values are simple (open, closed, etc.) and map cleanly to most destinations.
Conversations
Mapping requiredReplies and conversation threads are stored as related records to the parent ticket. We export the full thread in chronological order, preserving author (agent vs. customer), timestamp, and body content. HTML email bodies may need sanitization at import.
Internal Notes
Mapping requiredeTicket supports private agent notes attached to tickets. We migrate these as internal notes / private comments in the destination, preserving visibility scope (agent-only).
Attachments
Mapping requiredFile attachments are stored on disk with database references. We extract files from the configured upload directory and re-associate them with the parent ticket in the destination. Orphaned or missing files are flagged in the migration manifest.
Customers
Mapping requiredCustomer records derive from the email-sender field and any submitted form fields. eTicket does not maintain a rich CRM-style customer profile, so we extract email, name, and ticket-association count, mapping each customer to the destination's contact object.
Macros
Not in this platformeTicket does not ship a macro / canned-response engine comparable to modern helpdesks. Teams that have built saved replies via departmental templates must rebuild these in the destination.
SLAs
Not in this platformThere is no SLA timer or escalation policy engine in eTicket. SLA configuration must be created from scratch in the destination platform.
Custom Fields
Mapping requiredeTicket exposes basic configurable ticket fields. We inventory active custom fields by inspecting the database schema, then map them to destination custom fields. Any fields without a clear destination type are flagged for manual mapping.
| Object | Support | Notes |
|---|---|---|
| Tickets | Mapping required | Tickets are the primary object — created via email ingestion (pop3/pipe) or web form. We extract tickets from the eTicket MySQL database, preserving ticket ID, subject, status, priority, and assigned agent. Status values are simple (open, closed, etc.) and map cleanly to most destinations. |
| Conversations | Mapping required | Replies and conversation threads are stored as related records to the parent ticket. We export the full thread in chronological order, preserving author (agent vs. customer), timestamp, and body content. HTML email bodies may need sanitization at import. |
| Internal Notes | Mapping required | eTicket supports private agent notes attached to tickets. We migrate these as internal notes / private comments in the destination, preserving visibility scope (agent-only). |
| Attachments | Mapping required | File attachments are stored on disk with database references. We extract files from the configured upload directory and re-associate them with the parent ticket in the destination. Orphaned or missing files are flagged in the migration manifest. |
| Customers | Mapping required | Customer records derive from the email-sender field and any submitted form fields. eTicket does not maintain a rich CRM-style customer profile, so we extract email, name, and ticket-association count, mapping each customer to the destination's contact object. |
| Macros | Not in this platform | eTicket does not ship a macro / canned-response engine comparable to modern helpdesks. Teams that have built saved replies via departmental templates must rebuild these in the destination. |
| SLAs | Not in this platform | There is no SLA timer or escalation policy engine in eTicket. SLA configuration must be created from scratch in the destination platform. |
| Custom Fields | Mapping required | eTicket exposes basic configurable ticket fields. We inventory active custom fields by inspecting the database schema, then map them to destination custom fields. Any fields without a clear destination type are flagged for manual mapping. |
Gotchas
What to watch for in eTicket migrations
Issues we've hit on past eTicket migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Project is effectively dormant — latest release dates to 2008
No public API or vendor-supported export tooling
Attachments live on disk and can be orphaned
No SLA, automation, or modern routing engine
| Severity | Issue |
|---|---|
| High | Project is effectively dormant — latest release dates to 2008 |
| High | No public API or vendor-supported export tooling |
| Medium | Attachments live on disk and can be orphaned |
| Medium | No SLA, automation, or modern routing engine |
Leaving eTicket?
Where eTicket customers move next
7 destinations eTicket can migrate to.
How a eTicket migration works
Four steps, eTicket-specific
Connect
No public API — eTicket is a self-hosted PHP/MySQL application without a documented REST or developer interface. Integration relies on direct database access. into eTicket. Scopes limited to read-only on the data we move.
Map
We translate eTicket-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate eTicket quirks before production.
Migrate
Full migration with eTicket rate-limit handling. Rollback available throughout.
FAQ
eTicket migration FAQ
Answers to the questions buyers ask most during eTicket migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your eTicket migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate eTicket.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your eTicket setup and destination — written quote back within a business day.