Migrate your UVdesk data
Open-source PHP helpdesk with eCommerce roots and a generous free tier. It works well for small teams until ticket volume or custom-field complexity forces an upgrade path.
In its favor
Why people choose UVdesk
The signal that keeps UVdesk on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Free self-hosted option with no per-agent pricing makes UVdesk the lowest-cost entry point for budget-conscious support teams
eCommerce multi-channel integration with Bagisto and major marketplaces lets merchants centralize customer support without leaving their shop ecosystem
Social media app integrations automatically convert Facebook comments and Twitter mentions into support tickets for unified inbox management
One-click import paths for osTicket, Freshdesk, and Help Scout reduce migration friction when adopting UVdesk from those platforms
Prepared response automation speeds up agent reply times for recurring customer issue categories
Knowledgebase article ordering is broken by default—folder, category, and article display order fails to persist, forcing admins to delete and recreate content
Prepared response delays occasionally cause ticket reply backlogs, especially during peak volume periods when agents must fall back to manual responses
eCommerce integration capabilities are gated behind paid SaaS tiers, making the free Open Source edition significantly limited for online merchants
Self-hosted Open Source deployments require manual security patching and version upgrades, creating operational overhead for teams without DevOps capacity
Platform lacks the advanced SLA automation and enterprise reporting found in comparable tools like Freshdesk or Zoho Desk
Reasons to switch
Why people leave UVdesk
The recurring reasons buyers give for replacing UVdesk. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where UVdesk 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
UVdesk pricing overview
UVdesk uses per-agent monthly pricing on SaaS plans with a $11 Pro and $18 Enterprise tier, both requiring a minimum of 2 agents. The Open Source self-hosted edition is completely free with unlimited agents but omits the Knowledgebase and eCommerce integration modules.
Open Source
Tier 1 of 3
Free
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on UVdesk's schedule — see our quote-based pricing →
What gets migrated
UVdesk object support
Object-by-object support for UVdesk migrations. Per-pair details surface during scoping.
Tickets
Fully supportedTickets are the core UVdesk object. Each Ticket has a status (Open, Pending, Resolved, Closed), priority, type, mailbox source, assigned Agent, and linked Customer. We migrate Tickets 1:1 including thread history and custom properties.
Customers
Fully supportedUVdesk Customers represent end-users who submit tickets. Each Customer record includes name, email, and a company link. We preserve all Customer fields and their associated ticket history during migration.
Agents
Fully supportedAgents are support staff users. Each Agent has a role (Admin, Manager, Agent), status, and email. We map Agent records including their role designation and agent-level permissions to the destination system.
Groups
Fully supportedGroups in UVdesk are containers that assign Agents and Subgroups. Group membership determines ticket routing. We preserve Group names, descriptions, and user membership during migration.
Teams
Mapping requiredTeams are distinct from Groups and bundle specific Agents for targeted workload distribution. The destination system may not have an equivalent Team concept, so we map Team membership as a custom Agent property or group association.
Mailboxes
Mapping requiredMailboxes define the email inboxes that feed tickets into UVdesk. Mailbox settings include email addresses, IMAP credentials, and forwarding rules. We map mailbox-to-email-source associations but not IMAP credentials, which must be reconfigured at the destination.
Saved Replies
Mapping requiredSaved Replies are templated response texts Agents use to accelerate ticket replies. We migrate Saved Reply content and any category grouping, though usage statistics and agent-level saved-reply associations are not preserved.
Knowledgebase Articles
Mapping requiredKnowledgebase Articles are only available on UVdesk SaaS plans, not on the Open Source edition. We can migrate Articles, Categories, and Folders, but note that ordering and display configuration is frequently lost due to a known ordering bug in UVdesk.
Custom Fields
Mapping requiredUVdesk supports custom ticket fields added by admins. Custom field types include text, dropdown, checkbox, and date. We map custom fields 1:1 where field types are compatible; dropdown value lists require manual value mapping when the destination schema differs.
Workflows
Mapping requiredWorkflows are automation rules that trigger actions based on ticket conditions. We map Workflow rule names and conditions but not the full automation logic, which may require manual reconfiguration in the destination helpdesk.
Tags
Mapping requiredTickets can be tagged for categorization and filtering. We preserve tag strings and their ticket associations. If the destination system uses a different tagging model, tags are mapped as label or category fields.
Attachments
Mapping requiredTickets and replies may contain file attachments stored on UVdesk's file system or cloud storage. We migrate attachments by re-hosting files to the destination's storage and relinking them to the correct ticket thread entry.
Agent Performance Reports
Not in this platformAgent Insights reports and performance analytics are computed metrics stored in UVdesk's reporting layer, not as structured data records. We do not migrate reporting snapshots as they are not independently exportable via API.
Notes on Customers
Mapping requiredThe Notes on Customer feature adds visible notes attached to a Customer record that appear on all their tickets. We migrate customer notes as shared Contact notes or Customer description fields in the destination system.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Tickets are the core UVdesk object. Each Ticket has a status (Open, Pending, Resolved, Closed), priority, type, mailbox source, assigned Agent, and linked Customer. We migrate Tickets 1:1 including thread history and custom properties. |
| Customers | Fully supported | UVdesk Customers represent end-users who submit tickets. Each Customer record includes name, email, and a company link. We preserve all Customer fields and their associated ticket history during migration. |
| Agents | Fully supported | Agents are support staff users. Each Agent has a role (Admin, Manager, Agent), status, and email. We map Agent records including their role designation and agent-level permissions to the destination system. |
| Groups | Fully supported | Groups in UVdesk are containers that assign Agents and Subgroups. Group membership determines ticket routing. We preserve Group names, descriptions, and user membership during migration. |
| Teams | Mapping required | Teams are distinct from Groups and bundle specific Agents for targeted workload distribution. The destination system may not have an equivalent Team concept, so we map Team membership as a custom Agent property or group association. |
| Mailboxes | Mapping required | Mailboxes define the email inboxes that feed tickets into UVdesk. Mailbox settings include email addresses, IMAP credentials, and forwarding rules. We map mailbox-to-email-source associations but not IMAP credentials, which must be reconfigured at the destination. |
| Saved Replies | Mapping required | Saved Replies are templated response texts Agents use to accelerate ticket replies. We migrate Saved Reply content and any category grouping, though usage statistics and agent-level saved-reply associations are not preserved. |
| Knowledgebase Articles | Mapping required | Knowledgebase Articles are only available on UVdesk SaaS plans, not on the Open Source edition. We can migrate Articles, Categories, and Folders, but note that ordering and display configuration is frequently lost due to a known ordering bug in UVdesk. |
| Custom Fields | Mapping required | UVdesk supports custom ticket fields added by admins. Custom field types include text, dropdown, checkbox, and date. We map custom fields 1:1 where field types are compatible; dropdown value lists require manual value mapping when the destination schema differs. |
| Workflows | Mapping required | Workflows are automation rules that trigger actions based on ticket conditions. We map Workflow rule names and conditions but not the full automation logic, which may require manual reconfiguration in the destination helpdesk. |
| Tags | Mapping required | Tickets can be tagged for categorization and filtering. We preserve tag strings and their ticket associations. If the destination system uses a different tagging model, tags are mapped as label or category fields. |
| Attachments | Mapping required | Tickets and replies may contain file attachments stored on UVdesk's file system or cloud storage. We migrate attachments by re-hosting files to the destination's storage and relinking them to the correct ticket thread entry. |
| Agent Performance Reports | Not in this platform | Agent Insights reports and performance analytics are computed metrics stored in UVdesk's reporting layer, not as structured data records. We do not migrate reporting snapshots as they are not independently exportable via API. |
| Notes on Customers | Mapping required | The Notes on Customer feature adds visible notes attached to a Customer record that appear on all their tickets. We migrate customer notes as shared Contact notes or Customer description fields in the destination system. |
Gotchas
What to watch for in UVdesk migrations
Issues we've hit on past UVdesk migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Knowledgebase ordering silently fails on save
Knowledgebase unavailable on Open Source edition
Minimum 2-agent requirement on SaaS paid tiers
API lacks documented bulk endpoints and rate limits
eCommerce integrations gated behind paid SaaS tiers
| Severity | Issue |
|---|---|
| Medium | Knowledgebase ordering silently fails on save |
| Medium | Knowledgebase unavailable on Open Source edition |
| Low | Minimum 2-agent requirement on SaaS paid tiers |
| High | API lacks documented bulk endpoints and rate limits |
| Low | eCommerce integrations gated behind paid SaaS tiers |
Leaving UVdesk?
Where UVdesk customers move next
7 destinations UVdesk can migrate to.
How a UVdesk migration works
Four steps, UVdesk-specific
Connect
Not publicly documented into UVdesk. Scopes limited to read-only on the data we move.
Map
We translate UVdesk-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate UVdesk quirks before production.
Migrate
Full migration with UVdesk rate-limit handling. Rollback available throughout.
FAQ
UVdesk migration FAQ
Answers to the questions buyers ask most during UVdesk migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your UVdesk 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 UVdesk.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your UVdesk setup and destination — written quote back within a business day.