Autotask sync: the complete field-mapping reference

If you run Autotask, you already know its entity model: Companies, Contacts, Projects, Phases, Tasks, Tickets, Resources, TimeEntries, Contracts, and more. This page is the field-level reference for exactly how each Autotask entity maps into Current, which direction data flows, and who wins when both sides have touched the same field. Bookmark it — you'll come back to it.

For the plain-language version of how the connection is set up, see "Connect Autotask and choose what syncs". For the philosophy behind who owns what, see "Our methodology: your PSA stays the source of truth". For the schedule these pulls run on, see "How often does Current sync? Every schedule, in one table".

Autotask's REST API doesn't have one fixed address — each Autotask database lives on a numbered "zone," and your API credentials only work once Current knows which zone to call. When you first connect Autotask, Current calls Autotask's public zone-lookup endpoint with your API username. Autotask returns the correct API base URL and zone name for your account, and Current stores that base URL (not a secret) alongside your connection. Every sync call after that goes straight to your zone — there's no repeated lookup per request.

Companies are pulled from Autotask into the company record — this direction never reverses. Current never creates or edits a Companies record back in Autotask for existing synced accounts.

Current-only fields that live on the company record — like total MRR, MRR at risk, and lead source — have no Autotask equivalent and are never pushed. See "Mapping CRM industries to Autotask Market Segments" for how the market segment picklist specifically becomes the industry shown on the company record.

A contact you create in the CRM (in Current) is pushed to Autotask as a new Contacts record under that company. Once a contact exists in both systems, ongoing field refreshes (name, title, email, phone) still pull from Autotask — Autotask is the system of record for who a contact is.

Building a Current-native project in Autotask (from a playbook, template, or won quote) creates a new Autotask project by pushing project name, linked company, start/end dates, and the required type/status picklists. See "Building projects in your PSA from a template or won quote" and "Project modes: PSA-synced or Current-native" for when this conversion happens and why it's permanent.

Phases are read-only from Autotask's side — Current doesn't create or rename Autotask phases. See "Organize work with phases and tasks" for how phases work day to day.

Tasks carry the most fields of any synced entity, because task scheduling is where Current adds the most value over Autotask's own project module.

Task dates are Current's biggest ownership claim: after the very first pull, Current's dependency-aware scheduler owns start and end dates, and pushes them to Autotask — not the reverse. See "What is a critical path (and how Current finds it)" and "The Timeline view: drag to reschedule, and back-scheduling" for how those dates get set.

By default, two-way sync is off, and task fields simply refresh from Autotask on every pull. Turn it on in Settings → Integrations → Autotask, and six specific task fields become genuinely bidirectional: status, description, task type, department, estimated hours, and priority.

With two-way sync on, Current compares each field individually: if the incoming Autotask value is different from what Current last saw, and Autotask's own last-activity timestamp is newer than your last edit to that field in Current, Autotask's value wins. If your Current edit is more recent, it's kept — and the Autotask value is not marked as "seen," so a real change on the Autotask side that got deferred will still surface and be applied later rather than silently disappearing.

Autotask's TaskSecondaryResources are pulled into the task's list of assignees beyond the primary. When you change assignees in Current — adding or removing someone from a task — Current reconciles the whole list back to Autotask: newly added people are created as secondary resources, and removed people are deleted from Autotask's side. Current automatically picks a role each resource is actually eligible for in Autotask, so you don't get a role-mismatch rejection.

You can change a ticket's status from Current, which pushes back to Autotask. See "Logging time on a ticket vs. a task" for how ticket time entries work.

Resources are matched to Current user accounts by email, which is what drives account-manager and deal-owner auto-matching in the CRM. Internal cost rates feed "Holidays and employee costs: where the numbers come from."

See "Logging time and how it reaches your PSA's billing" for the full time-entry-to-billing flow, and the companion article "What Current writes back to Autotask (and when)" for exactly what's included on the outbound time entry push.

Contracts and their services are inbound only — Current reads your Autotask contracts to power revenue and coverage reporting, and never edits a contract.

Autotask holidays (from your configured holiday sets) pull in as read-only calendar entries — date and name — used by the scheduler to avoid booking work on days off. See "PTO and availability-aware scheduling in the Timeline". If your Autotask zone doesn't expose the Holidays entity, this pull is skipped quietly rather than failing your whole sync.

Company notes are the one entity where Autotask and Current genuinely share write access, with a simple rule: whichever side authored a note owns it. Notes pulled in from Autotask get refreshed on re-sync; notes you write in Current and push to Autotask are left alone by later Autotask pulls. Notes you push from Current are always created as internal — a pushed note never becomes visible on the Autotask client portal.

Autotask's various status and type fields are picklists — numeric ids with zone-specific labels. Current resolves these live from Autotask's field metadata (not a hardcoded list), so a picklist you've customized in Autotask is read correctly. Task and ticket status specifically collapse Autotask's many possible labels into Current's own simplified stages (backlog/in progress/review/done for tasks; open/assigned/pending/resolved/closed for tickets) by matching keywords in the label — a status labeled anything containing "complete" becomes done, anything with "progress" becomes in progress, and so on. The original Autotask status id is always kept alongside the simplified stage, so nothing is lost in translation.

• ＋Company, contract, contract-service, company-ticket, and company-note pulls are all read-only by design — Current never patches these Autotask records except through the specific CRM push flows described in "What Current writes back to Autotask (and when)".
• ＋Project health scores are Current-only — there's no Autotask equivalent field.
• ＋Total MRR, MRR at risk, and renewed MRR shown in the CRM are computed in Current and never pushed to any Autotask field.
• ＋Task worked-hours are computed from real logged time entries, never from Autotask's estimated/remaining hours math.
• ＋Calendar appointments only sync as a generic "busy" marker — the real appointment subject line is never pulled, so a private subject never leaks tenant-wide.
• ＋Once imported, ticket due dates and assignment become Current-owned and are not overwritten by later Autotask pulls.