PSA Data Export guide
Export Kaseya BMS data
Kaseya BMS’s New Service Desk provides an Export batch action for selected tickets. Choose columns and views deliberately, then inspect the resulting file against the selected ticket population.
On this page
Choose the native export
Kaseya BMS’s New Service Desk provides an Export batch action for selected tickets. Choose columns and views deliberately, then inspect the resulting file against the selected ticket population. See New Service Desk experience.
Prepare a usable archive
Keep finance, account/contact and worklog extracts in the inventory alongside ticket rows. Confirm the actual export format and note/file coverage with a sample; the reviewed UI guide establishes the action rather than a full archive specification. Related official guidance: Importing data.
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Tickets and notes | Source ticket ID, client/requester, status, dates and custom fields; join notes and files by parent ID |
| Accounts and contacts | Source person/company IDs, names, email and parent organization/site; preserve inactive and duplicate-name mappings |
| Contracts and time entries | Technician ID, ticket/customer link, work date, duration units, billable status and source entry ID |
| Invoices and finance records | 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.
Prepare for the Autotask destination route
Kaseya documents BMS to Autotask Ultimate separately from ordinary BMS exports. Separate currently listed objects from items labelled coming soon. Preserve ticket attachments and custom fields outside the transfer package. Pair the source inventory with the Autotask import guide and agree the actual service scope before cutover.
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.