Connect Syncro and choose what syncs

Syncro is a first-class PSA in Current, the fourth alongside Autotask, ConnectWise and HaloPSA. Syncro stays the source of truth for time, billing and invoicing; Current owns scheduling and the views your team lives in. Customers, contacts, leads, tickets, estimates, contracts, recurring invoice schedules, users and time all flow in, and the writes you allow flow back.

• ＋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.

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.

1. 1
   Open Settings, Integrations, Syncro

   Only Tenant Admins see this page.
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.

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.

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.

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.

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

• ＋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 or Syncro 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.