PSA Data Export guide
Export ConnectWise PSA data
Choose screen/report exports for the fields you can verify, and scope historical database delivery with ConnectWise when you need a retained source database. Confirm hosting eligibility, delivery contents and terms in your authenticated account before relying on that service.
On this page
Choose the native export
Choose screen/report exports for the fields you can verify, and scope historical database delivery with ConnectWise when you need a retained source database. Confirm hosting eligibility, delivery contents and terms in your authenticated account before relying on that service. See Historical Database and Merge Options for Mergers and Acquisitions.
Prepare a usable archive
Confirm the source hosting model, database delivery terms and required ticket-note/file scope. The canonical support pages currently redirect repeatedly; request the current templates through an authenticated support session. Related official guidance: Company and Contact Import.
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Service tickets and notes | Source ticket ID, client/requester, status, dates and custom fields; join notes and files by parent ID |
| Companies and contacts | Source person/company IDs, names, email and parent organization/site; preserve inactive and duplicate-name mappings |
| Time entries | Technician ID, ticket/customer link, work date, duration units, billable status and source entry ID |
| Agreements and invoices | Document and customer IDs, line items, currency, tax, totals, balances and payment allocations; reconcile financial meaning |
Validate formats and attachments
Open CSV or spreadsheet output with dates and identifiers intact. Validate JSON pagination and error handling. Download and verify file contents as well as metadata while authenticated or time-limited URLs remain accessible.
Prepare for migration
Count records by type and year, sample the oldest and most complex items, save field dictionaries, and document missing modules. Use the PSA migration checklist before cancellation.
Keep the source history useful
Store the original export, field definitions, file manifest and validation results together. Follow the source archive planning use case and keep the archive readable after cutover.
Preparing a move to Autotask
The destination-owned Autotask implementation checklist names a ConnectWise migration route. Arrange the client ID and API credentials early. Its exclusions include invoice history, agreements, expenses, procurement and configuration items. Assign each relevant item an export or archive owner before cancellation. Follow the Autotask import guide for destination preparation; this route is separate from ConnectWise to Syncro.
Scope ticket and Excel reporting exports
Choose the PSA screen or report whose fields answer the business question. Before saving its output, record the selected filters, columns and intended record count. Verify the format available in that screen; a CSV opened in Excel and an Excel workbook are different outputs. Compare an old closed ticket and its notes, time and files with the retained result before relying on it as conversation history.
Include configuration records in the export plan
Configuration records need their own inventory and documented extraction route. Agree the required fields, company relationships and file scope with the PSA administrator, then obtain the current ConnectWise PSA instructions through support. Confirm completeness with a representative configuration before expanding the extraction. ConnectWise Automate scripts, XML imports and RMM device exports are separate product workflows.
Plan your independent PSA archive
Keep source history available after your move. Join the waitlist for invitation-only BackupPSA access, or contact us about your platform.