Skip to content
Current

Connect Syncro and choose what syncs

Create the Current user and its API token in Syncro, switch parent/child tickets on, paste the subdomain and token in Current, and see what the first sync pulls.

Updated 3 min read
On this page · 9 sections
  1. What it does for you
  2. Before you start
  3. Create the API token in Syncro
  4. The permissions to tick
  5. Connect in Current
  6. The delta poll, and why Syncro can be slower
  7. Projects are parent tickets, and they are opt-in
  8. Who owns which field
  9. Disconnecting, and switching PSAs

Connect Syncro and its customers, tickets, estimates, recurring invoices and time land in Current. An approved estimate becomes a project with its charges, each company page shows its tickets and monthly recurring revenue, and business reviews are drafted from the tickets your team closed.

What it does for you

Where in CurrentWhat you get
Service desk ticketsSyncro tickets appear in ticket search beside your desk tickets, open and closed. Once a tenant admin turns on Ticket and time sync, each desk ticket shows its matching Syncro ticket (or lets you link an existing one), and desk tickets, their notes and their time are kept in step with Syncro, so billing still happens where it always has.
Company pageEach customer's Syncro tickets, its contracts with monthly recurring revenue read from the recurring invoice schedules, its estimates as quotes, and the invoice lines behind account profitability, so an account manager sees service load and revenue in one place.
AlertsAn urgent ticket, a security incident or an unhappy customer on a company alerts its account owner by bell and email, and a stalled or failing sync rings a tenant admin's bell with a link to Sync health.
My DayThe Syncro project tasks assigned to you sit in today's work (with the service desk on, your Syncro tickets too), approved estimates wait in Won quotes to convert, and the time you log goes to Syncro as a timer entry against a Labor product.
Reports and dashboardsTickets opened, closed and still open, with close times, on dashboards and in the Service report, read from the same Syncro tickets your team works.
Business reviewsTickets, projects and contracts fill the service delivery part of each review, so it is drafted from the work your team closed.
SalesSyncro Leads in a sales status become opportunities in your pipeline, approved estimates turn into projects and charges in a few guided steps, contracts feed the whitespace grid, and urgent or unhappy tickets on your accounts show in Hot tickets on Sales home.
Ask CurrentAsk about a customer and Ask Current answers from its Syncro tickets and contracts, with a link to each ticket it used. Contract values show only to people allowed to see money.

Syncro stays the source of truth for time, billing and invoicing; Current owns scheduling and the views your team works in. Customers, contacts, leads, tickets, estimates, contracts, recurring invoice schedules, users and time all flow in, and the writes you allow flow back.

Note
New as of September 2026
Syncro support is new, so a few Syncro-specific behaviours are still being confirmed against live accounts. They are called out as "still being confirmed" where they appear. Everything is built to fail safe in the meantime: a value Current cannot read cleanly is left alone rather than overwritten, and nothing is guessed.
The Syncro card on Integrations once it is connected: when it last synced, whether anything is waiting in conflict, and the way in to Manage and Sync now.
Note
One PSA per workspace
Current syncs one PSA at a time: Autotask, ConnectWise PSA, HaloPSA, Syncro, Rev.io or SuperOps, chosen at signup and switchable later. If another PSA is connected, the Syncro card asks you to disconnect it first, and the rule is enforced in the database, not just the interface. See "Autotask, ConnectWise, HaloPSA, Syncro, Rev.io, or SuperOps: choosing your PSA".

Before you start

  • A Syncro administrator login, so you can create a security group, a user and an API token.
  • Your Syncro subdomain: the first part of the address you sign in at, as in yourcompany.syncromsp.com.
  • Tenant Admin role in Current. Integrations are an admin-only action.
  • Ten minutes in Syncro first if you want the smoothest first sync. "Prepare your Syncro before onboarding: the setup checklist" walks the whole list.

Create the API token in Syncro

  1. 1
    Make a security group for Current
    In Syncro, go to Admin, Syncro Administration, Security Groups and create a group named Current. This group is what the token can reach, so it is where you decide how far the sync sees.
  2. 2
    Give the group Ticket Parent-Child, Edit
    Current builds a project as a parent ticket with child tickets under it, so this permission is required. Without it every project and task create comes back as a permission error rather than a project.
  3. 3
    Switch parent/child tickets on for the account
    Admin, Tickets, Preferences. Turn on parent/child tickets and ticket due dates. This is an account-wide setting, separate from the permission above, and both are needed.
  4. 4
    Create a user named Current in that group
    Every Syncro API token belongs to a person, so the work Current does is attributed to whoever owns the token. A dedicated user keeps your technicians' names off records Current wrote, and keeps the permissions in one place.
  5. 5
    Create the token as that user
    Sign in as the Current user, open Profile, API Tokens, New Token, and choose Custom Permissions. Tick the permissions listed below, create the token, and copy the key straight into a password manager. Syncro shows the key once.

The permissions to tick

AreaPermissions
CustomersList/Search, View Detail, Create, Edit
TicketsList/Search, View Details, Create, Edit
Ticket Parent-ChildEdit
Ticket TimersOverview
EstimatesList/Search, View Details, Edit
ContractsList/Search
Recurring InvoicesList
InvoicesList/Search, View Details
LeadsList/Search
AppointmentsView All
ProductsList/Search
AssetsList/Search, View Details (only if you want the Syncro Assets feed)
RMM AlertsList (only if you want the Syncro Assets feed)
Note
The last two rows are optional
Assets and RMM Alerts are only needed for the Syncro Assets feed, which reads a company's machines, patch state, installed software and open alerts. Leave them unticked if you do not want it, and add them later without creating a new token. Everything above them is needed for the PSA sync itself.
Note
A passing test proves the token, not every permission
The connection test signs in with the token and makes one cheap read. A permission you missed shows up at the first sync instead, as a named gap on the connection card and on Sync Health rather than as empty data. If a whole area comes back blocked, the card names the area and the permission to add.

Connect in Current

  1. 1
    Open Settings › Integrations and press the Syncro row
    The drawer opens with its card. Only Tenant Admins can connect it or change its keys; anyone else who opens it sees a short summary.
  2. 2
    Enter your subdomain and API token
    The subdomain is not a secret. The token is, and once stored it is kept server-side only and never sent back to the browser.
  3. 3
    Run Test and save
    Current reads the token owner and one page of customers to prove the credentials are real before anything is stored.
  4. 4
    Nothing has synced yet, and that is deliberate
    Connecting stores the connection only. No data moves until the first sync runs, so you can connect, review the sync switches, and pull when you are ready.
  5. 5
    Start the first sync
    Customers, contacts, users, tickets, estimates, contracts, recurring invoice schedules, invoices and time come across. Large accounts take a while, because Syncro's API budget is shared across every workspace connected to it, so Current paces itself and resumes where it stopped.

The delta poll, and why Syncro can be slower

After the first pull, Current polls Syncro for changes on a schedule, and pushes go out as they happen rather than waiting for the poll. Syncro's rate limit is 180 calls a minute per address, shared by every workspace Current syncs with Syncro, so Current works to a fair share of that budget instead of racing for it. A minute where the budget is spent is not an error: the sync picks up where it left off on the next run, and the card says so rather than showing a failure.

Projects are parent tickets, and they are opt-in

Syncro has no project record. A project in Syncro is a parent ticket with child tickets under it. Current tracks the parent tickets it created, plus the ones you pick from the "Projects from Syncro" list on the card. Nothing is adopted for you, because plenty of shops use parent and child tickets for grouping that is not project work. There is an optional rule that adopts new parent tickets whose issue type is Project, and it is off until you turn it on.

Who owns which field

The field-ownership map keeps the two systems from fighting. Current never overwrites a Syncro-owned field on push, and a Syncro pull never clobbers a Current-owned field.

Syncro ownsCurrent owns
Ticket subject, status, assignee and due dateTask scheduling and dependency dates
Time entries, billing status and invoicingCritical path and milestone flags
Customers, contracts, recurring schedules and estimatesProject health, phases and estimated hours

For the field-by-field detail, see "Syncro sync: the complete field-mapping reference".

Disconnecting, and switching PSAs

  • Disconnect lives in the Manage drawer's danger zone and asks you to type DISCONNECT. It stops all syncing and deletes nothing already pulled.
  • Projects that were syncing to Syncro freeze rather than break: they keep their data, show a synced-to-a-disconnected-PSA state, and make no Syncro calls until you reconnect.
  • Switching to Autotask, ConnectWise, HaloPSA, Rev.io or SuperOps is disconnect then connect, from the other provider's own card.
  • Switching is free on a fresh workspace. Once you have synced a real book from Syncro, connecting a different PSA is blocked at connect time so the two providers' records cannot collide on their ids. Email support@current.day and we will run a guided migration first.
Heads up
Reading is the default, writing is gated
Pulling from Syncro is always on once connected. Writing back is gated twice: the two-way sync switch in the Manage drawer controls task and project pushes, and CRM write mode, off by default with a test mode in the middle, controls every CRM write. See "What Current writes back to Syncro (and when)".
Was this helpful?
← Previous
Slide: boxes, protected systems, backup history and the restores you ran
Next →
Prepare your Syncro before onboarding: the setup checklist

Related articles