How to export tickets from ConnectWise Manage before you cancel
Three routes get ticket history out of ConnectWise Manage: CSV exports from the service board and ticket search grids, scripted pulls through the ConnectWise REST API, or a third-party export service that does the API work for you. To export tickets from ConnectWise Manage with notes, time and attachments intact, the API is the only complete route. Grid exports give you a list of tickets, not their history. Here is how to run each route, check the result and keep the archive usable, inside a working day.
Decide what you actually need before you export anything
The common mistake is treating the export as one job. It is three: the ticket records, the conversation on each ticket, and the evidence attached to it. They come out by different routes, and a CSV that looks complete usually contains only the first.
- Ticket headers: number, summary, company, contact, board, status, priority, type and subtype, dates opened and closed, assigned resource. Easy to get.
- Notes: the discussion, internal analysis and resolution text. This is the part you will search for in two years. Harder to get.
- Time entries: who worked, how long, against which agreement. Matters for billing disputes and for any client asking what their contract bought them.
- Attachments: screenshots, logs, signed forms. Stored separately as documents and easy to forget.
The two-year test: pick a ticket a client might dispute two years from now and ask whether your export would let you answer them. If the answer needs the notes or the time, a grid export alone fails.
Route one: grid and report exports
The ticket search and service board views in Manage can be exported to a spreadsheet. Build a search that covers every board and every status, including closed, add the columns you want, and export. Large histories may need splitting by date range so each export finishes cleanly.
If you licensed Report Writer, you can query the underlying tables directly and pull more fields in one pass, including note text, though long notes can be truncated depending on how the report is built. Check before you rely on it.
Use this route for a fast index of every ticket. Do not use it as your archive. Skip the API step and you will discover the gap the first time someone asks what was actually done on a job.
Route two: the ConnectWise REST API
The API is what migration tools themselves use, and it is within reach of anyone comfortable with PowerShell or Python. You need an API member with read access to service, time and documents, plus a client ID registered on the ConnectWise developer portal. Create these early: if access ends before the work is done, there is no recovering it.
The endpoints that matter:
- Tickets:
/service/tickets, paged, with conditions on date ranges to keep each pull manageable. - Notes:
/service/tickets/{id}/notesfor each ticket, or the all-notes endpoint where your version supports it. - Time:
/time/entries, filtered by charge-to type so you collect service ticket time. - Attachments:
/system/documentsfiltered to the ticket record, then download each file.
Write each ticket to its own JSON file, named by ticket number, with notes and time nested inside, and put attachments in a matching folder. The API is rate limited, so build in retries and log any ticket that failed. A run across a large history takes hours, which is why you start it in the morning, not on the last afternoon of your contract.
Route three: export and migration services
Several services will pull Manage data and either hand you an archive or load it into a new PSA. They suit you if nobody on the team scripts, or if you want tickets imported rather than archived. Ask each one which fields they carry, whether internal notes stay marked as internal, how attachments are handled and what you receive if the import into your destination fails. Get the field map in writing.
If you are moving tickets into a new PSA rather than archiving, the wider sequence is covered in our guide to moving tickets, agreements and billing out of ConnectWise Manage.
Which fields survive, and which do not
| Data | Grid export | API |
|---|---|---|
| Ticket headers and status | Yes | Yes |
| Full note text | No, or partial | Yes |
| Internal versus external flag | No | Yes |
| Time entries | Separate export | Yes |
| Attachments | No | Yes, downloaded separately |
| SLA timings and audit trail | Limited | Partly |
What rarely survives anywhere is context: workflow rules, board automations and the meaning of your custom statuses. Write a one-page key explaining your boards and statuses and store it with the archive. Future you will not remember what "Waiting Vendor 2" meant.
Verify the export the same day
An unverified export is a hope wearing a folder structure. Run three checks before you sign anything off:
- The count test: total tickets in Manage against total files or rows in your export, per board and per year. Any mismatch points at a failed page.
- The sample test: open ten tickets at random, old and new, and compare notes, time and attachments with what Manage shows.
- The awkward ticket test: find your longest ticket and one with many attachments. These are where truncation and timeouts hide.
Keeping the archive searchable
A pile of JSON is complete but useless to a service desk. Load the files into something you can query: a small SQLite or Postgres database, a spreadsheet index with links to each ticket file, or a search tool pointed at the folder. The minimum is being able to search by company, ticket number and words in the notes.
Store the archive somewhere backed up, restrict it to people who should see client data, and decide how long you keep it. Old tickets contain names, addresses and sometimes credentials pasted into notes, so treat them under your data protection obligations rather than as a forgotten share. Check your notice dates too: our piece on cancelling a ConnectWise contract covers when access is likely to matter.
Where this fits with Helios
Most of this is discipline, not tooling: the export happens in ConnectWise, and no destination can rescue notes you never pulled. Helios includes a helpdesk with SLA clocks, client portals and time tracking billed into Xero or QuickBooks, so new tickets have a home once the old ones are archived. Our service desk documentation shows how tickets are structured, which helps you decide whether to import history or keep it as a searchable archive alongside.
Common questions about exporting ConnectWise tickets
Should I import old ConnectWise tickets into my new PSA?
Importing old ConnectWise tickets into a new PSA is worth it for open tickets and perhaps the last year of history, because technicians search recent work. Older tickets are usually better kept in a searchable archive, since imports often flatten notes, lose internal flags and cost more time than the history is worth day to day.
Can I export ConnectWise Manage ticket attachments?
ConnectWise Manage ticket attachments can be exported through the REST API by listing documents linked to each ticket and downloading every file. Grid and spreadsheet exports do not include them. Save attachments in a folder named after the ticket number so each file stays tied to the ticket it belongs to.
What format is best for a ticket archive?
The best ticket archive format is JSON per ticket for completeness, loaded into a simple database or search index for day-to-day use. JSON keeps notes, time entries and metadata together without truncation, while the database lets anyone search by company, ticket number or note text without needing to read raw files.
Read next
Why MSPs choose Helios
One platform that does the work, at a price that stays put
Helio fixes, not just flags
When an alert fires, Helio, the AI technician built into Helios, investigates it, writes the fix and runs it once you approve. It keeps what works, so the next one is quicker.
Everything in one product
RMM, a service desk with SLAs, patching including third-party apps, remote access, Microsoft 365 and Defender checks, backup monitoring, a client portal and billing into Xero or QuickBooks.
Priced by fleet, not by people
£4 a device on Launch up to 25 devices, from £20 a month, then £99, £199 or £399 a month by fleet size, with any number of technicians and every feature on every plan.
A price that stays put
Your price is locked for as long as you stay subscribed, and that is written into our terms. Monthly billing, cancel any time.
Bring your clients across
Import your clients and machines from another RMM's CSV export, then roll the Helios agent out at your own pace, with a count of how many have arrived.
14 days free, no card to start
The full platform from the first minute, on your own machines. No sales call. Remote control asks for one card check, and nothing is charged.
See it on your own fleet
Helios is the AI-native platform for MSPs: monitoring, patching, security, Microsoft 365, backup monitoring, remote access, client billing and an AI service desk in one product, at one flat price per MSP. Contracts and logged time become invoices in Xero or QuickBooks without leaving the platform. Every feature is on every plan. 14-day free trial, card-free, set up in minutes, cancel any time.
Start freeResearched and written with Helio SEO, our AI writer for business blogs.