Migrate your Autotask Professional Services Automation (PSA) data

Tickets are the core service desk object in Autotask. They support custom Ticket Fields (UDFs), status/lifecycle management, queue assignment, and attachments. We map Tickets field-for-field and preserve the full Ticket Field schema including any UDFs the customer has defined.

Company records in Autotask serve as the account/company object. They link to Contacts, Tickets, Projects, and Contracts. We export Companies with their full address, billing, and organizational data and map them to the destination account or company object.

Contact records in Autotask hold the individual person data with a link to their parent Company. Contact-level UDFs are supported. We preserve Contact-to-Company linkage during migration to maintain the CRM relationship structure.

Autotask Projects contain Tasks, milestone dates, resource assignments, and budget tracking. Project status, phases, and custom fields carry over. We map Projects as the top-level container and include their associated Tasks and resource allocations.

Contracts in Autotask define billing arrangements, labor rates, service level terms, and recurring billing rules. We export Contracts including the associated billing rate cards so that service contract terms survive the migration intact.

Time entries in Autotask are linked to Tickets, Projects, or standalone task work. They capture hours, date, owner, and optional notes. We export time entries with their parent object reference so billing history is preserved in the destination system.

UDFs exist on multiple objects (Tickets, Companies, Contacts, Projects, Contracts, etc.) and can be text, number, date, dropdown, or checkbox types. The UDF schema is customer-specific and must be recreated or mapped per-object during migration. We capture the full UDF definition set before export and build a mapping table for the destination.

Service Calls are Autotask's scheduling and dispatch object for field service appointments. They do not have a documented export path in the REST API. We do not migrate Service Call records; the customer must manually recreate these in the destination system.

To-dos in Autotask are individual action items tied to users, not to tickets or projects. They lack a bulk export API endpoint. We flag these for manual migration or conversion to task records in the destination platform.

Autotask has a Document Management module for attaching files to Tickets, Projects, Contracts, and other objects. Documents are accessible via API but require separate attachment handling. We map document references and note which files require manual re-upload to the destination.

Autotask workflow automation rules are configuration objects with no export capability via the REST API. Every rule must be manually reviewed and rebuilt in the destination PSA. We provide a workflow audit checklist during scoping to capture rule logic before migration.

Resource records represent technicians and staff who are assigned to Tickets, Projects, and Service Calls. We export Resources with their role, department, and license status so that owner assignments resolve correctly in the destination system.

File attachments on Tickets and Projects are stored in Autotask's document management system. The REST API supports attachment retrieval but the process requires sequential per-attachment calls. We chunk large attachment sets and handle re-upload with mapped parent record references.