Table of Contents
“Can I export my data if I leave my PSA?” is one of the first questions MSP owners ask a few weeks before their PSA renewal date. The answer is almost always yes. Every PSA vendor will tell you the data is yours, and most give you an export button to prove it.
What that button produces is another matter. A PSA data export can arrive as a neat set of linked records, or as a pile of flat CSV files where tickets no longer know which client they belong to. Which one you get decides whether switching PSA takes a weekend or a quarter. You can find out in about 20 minutes, well before your notice period runs out.
Short answer
Yes. You own the data in your PSA, and almost every PSA software lets you export it. The catch is the format. A typical PSA data export gives you a set of flat CSV files with the links between tickets, contacts, assets, time entries and invoices stripped out. A 20-minute test export shows you which kind you have before your renewal date forces the question.
PSA data export: quick answers
| Question | Answer |
|---|---|
| Do I own my PSA data? | Yes. Your vendor holds your business data. It does not own it. |
| Can I export my PSA data to CSV? | Usually. Check whether the CSVs keep the IDs that link tickets to clients, contacts and time. Without them, the data loses its history when you import it elsewhere. |
| How long does a PSA data migration take? | Technicians can usually work in a new PSA within the first week. Full cutover takes longer. See the PSA migration timeline guide. |
| Should I test my PSA data export now? | Yes. A test export takes about 20 minutes, carries no risk and changes nothing in your live system. |
What does owning your PSA data actually mean?
Most MSP owners ask this question a few weeks before a renewal, after a price increase or a support ticket that went nowhere. Every vendor says the data is yours. That is legally true. Having it in a form you can use somewhere else is a separate question, and it is the one that decides how locked in you are.
Many older PSA platforms were built around a relational database with a basic export bolted on later. Getting tickets, time and billing out together, with their links intact, was never the priority. The longer you run on a platform, the more workflows, custom fields and history pile up inside it, and the harder a clean PSA data export becomes. That is how PSA vendor lock-in usually works in practice. Nobody stops you leaving. The data just comes out in a shape that makes leaving expensive.
For an MSP with 3 to 10 technicians, there is rarely a database contractor on call to write a custom extraction script against a REST API. So the owner ends up rebuilding the links by hand on weekends, or gives up on the switch and renews another year.
A rough cost of a manual rebuild (illustrative): 2,000 open and recent tickets that need re-linking to clients and contacts x 1 minute each to match by hand = about 33 hours of owner or senior tech time before the new PSA is useful
That number grows with every year of history you try to bring across. It is also why so many owners stay on a platform they complain about: the export problem feels bigger than the problem they already have.
How does a typical PSA data export work?
Say you are ready to switch PSA. You click export and download a CSV. It holds your active and archived tickets. What it often leaves out are the IDs that tell you which client each ticket belongs to, which site it sits under and which agreement it falls under. A flat PSA data export tends to look like this:
- Tickets: ticket ID, title and description, but no link to the client account or agreement.
- Contacts: first name, last name and email, but no link to their company.
- Time entries: hours, date and ticket ID, but no invoice status or agreement link.
- Assets: serial number and device name, but no link to the client, site or department.
Each file arrives on its own and none of them reference each other. Before the data is usable, someone has to rebuild those connections by hand, and a simple PSA data export turns into a full PSA data migration project.
Three things that break a PSA data export
Three problems show up when you ask for a full PSA data export. Knowing which are real technical limits and which are design choices helps you set expectations before you switch PSA.
1. CSV files lose the relationships
A PSA is a relational system. Tickets connect to time entries, assets, contacts and contracts. A flat CSV export drops those connections, so thousands of records have to be reassigned manually after import.
2. API rate limits slow bulk exports
If the only route to a full PSA data export is the REST API, you will hit its rate limit quickly. Rate limits protect the vendor’s servers, but a low limit can stretch a pull of five years of ticket history into days or weeks unless the platform offers a bulk export tool.
3. Ticket notes come out as raw HTML
Ticket notes, internal resolutions and client replies are often stored as formatted text. On export, that formatting can turn into raw HTML tags inside the text, which makes older tickets hard to read once they land in a new PSA.
Question to ask any vendor before you sign: “Can I export my full database with IDs and relationships intact, or will I get disconnected flat files?”
The 20-minute PSA data export test
You do not need a migration plan to find out where you stand. Pull one export from your current PSA this week and open it next to the checklist below. If the files fail two or more checks, plan for cleanup time before you switch PSA, and start well before your renewal notice date.
Why MSP owners stay on a PSA they dislike
The export problem explains part of PSA vendor lock-in. The rest is behaviour. When an MSP owner keeps paying for a platform they regularly complain about, it is rarely because they are happy with it. Known problems feel safer than unknown ones.
- The known devil: you know every flaw in the current system, and starting over feels like more disruption than it is worth.
- Sunk cost: “We spent months configuring workflows and training the team.” That time is already spent. Staying on a slow system does not recover it.
- Decision fatigue: comparing PSA software without a clear framework takes so long that the renewal date arrives first and the contract rolls over.
A test export cuts through all three. It replaces a vague worry with a specific answer about your own data.
What your contract decides about PSA vendor lock-in
Before you plan an exit, read the agreement that governs your account. Your contract usually decides how locked in you are far more than any export tool does. The points below are general information only, not legal advice, and terms vary a lot between vendors.
Also read: MSP vendor lock-in: 8 clauses to check before you sign
How much the law protects you depends on where you operate:
- Australia: the ACCC unfair contract terms regime has allowed penalties for unfair terms in small business contracts since November 2023. It covers contracts where one party has fewer than 100 employees or turnover under $10 million, so Australian MSPs have real statutory protection.
- United States: the FTC click-to-cancel rule was vacated by the Eighth Circuit in July 2025, so no federal cancellation rule now covers your PSA contract.
- United Kingdom: the DMCCA subscription contract rules are due to start in January 2027 and are written around consumer contracts. Do not rely on them for a B2B agreement.
Where the law does not step in, the written contract sets your options. Check your master services agreement and order forms for:
- Renewal date and notice period: the exact renewal date, the notice window (often 30, 60 or 90 days) and how notice must be delivered.
- Access after notice: admin and API access should continue until the last day of your final paid billing period, so your PSA data export is not cut off early.
- Export terms: any fee for a full database export, or a requirement to use proprietary software to restore it.
- Rollover clause: whether missing the notice window rolls you into a new multi-year term.
How to switch PSA without losing your data
- Check your contract dates. Note the renewal date and the last day you can give notice. That is your hard deadline.
- Run a test PSA data export. Pull tickets, assets, contacts and time entries, and check they open and read correctly.
- Audit the files. Confirm tickets still carry their client links and that no fields are corrupted. Use the five checks above.
- Take a full backup while you still have access. Export everything before you tell your vendor you are leaving.
- Move active data only. Bring across active clients, open tickets, live projects and unbilled time. Archive closed tickets locally, or keep the old PSA in read-only mode for lookups.
- Test the import mapping. Make sure the data maps correctly in the new PSA before you cut over.
- Send formal notice. Give written cancellation notice inside the notice period.
- Run a final delta export. Just before access ends, export once more to catch tickets and time entries created during the switch.
Setup in a new PSA can be quick when the platform does not gate you behind onboarding. Tahl Jenkins of Mt Warning IT had Gorelo set up in about three hours and was fully running within a week. For a phase-by-phase plan, read the guide to switching your PSA/RMM.
What low PSA vendor lock-in looks like
Gorelo is a unified PSA and RMM built for small MSPs, and it keeps the commercial exit simple:
| Term | Gorelo |
|---|---|
| Contract | No lock-in contracts |
| Pricing | Full Platform $99/user/month billed yearly. PSA Only $59/user/month for non-technical staff (pricing as of October 2026) |
| Onboarding | Operational from trial, with no mandatory onboarding fee |
| Data access | Documented API with scoped keys |
| Trial | 30 days free |
Every vendor has a reason to make leaving hard. The fairest test of any PSA software, including Gorelo, is to run the same 20-minute PSA data export during the trial and see what comes out.
How data export works in Gorelo
Gorelo splits data export across two routes. Clients, contacts and products can be bulk exported and imported by CSV from the CRM, and product and bundle lists also export to CSV. Everything else goes through the Gorelo API.
API keys are created in Settings under Integrations, and each key gets its own permission scope. That way, a migration or reporting script only touches the data it needs. The API runs on separate US and Australian endpoints, each with a live Swagger reference that lists every available call.
The same API works in the other direction when moving into Gorelo. Closed tickets and their comments can be imported with their original dates, and importing history doesn’t trigger notifications to clients or technicians.
Run the 20-minute PSA data export test against this during the trial. Check which records come out by CSV, which need the API, and whether the IDs that link them survive.
Final Thoughts
Before you commit your MSP to any platform, find out what your data looks like when it leaves. A PSA data export test takes 20 minutes, costs nothing and tells you how much control you really have over your client history.
If you run an MSP with 2 to 30 people and want to see how a unified PSA and RMM handles your workflows, start a 30-day free trial of Gorelo and run the same export test there.
Can I export all my data from my current PSA?
Usually, yes. How complete the PSA data export is depends on the vendor’s export tools and API limits. Run a test export and check it against your client records before you send a non-renewal notice.
Who legally owns the data in a PSA?
You own your business data. PSA vendor lock-in comes from technical barriers such as API rate limits and flat files with no IDs linking them, plus contract terms like notice periods and rollover clauses.
How long does a PSA data migration take for a small MSP?
For an MSP with 2 to 30 people, technicians can often work in the new PSA within the first week. Full cutover usually takes a few months and depends more on client communication and data cleanup than on the import itself. The PSA migration timeline guide breaks down each phase.
What should I check in a PSA contract before I switch PSA?
Check the renewal notice period, API and admin access after notice, any fees for a full data export, and whether a missed notice rolls you into a new multi-year term.
What is the fastest way to check my MSP data portability?
Export tickets, contacts, assets and time entries from your PSA, then confirm each ticket still carries a client ID and contact ID, notes are readable and time entries show billing status. If two or more checks fail, expect cleanup work during a PSA data migration.
