Connect ConnectWise PSA and choose what syncs
ConnectWise PSA is a first-class PSA in Current — the same depth of two-way sync Autotask and HaloPSA get. ConnectWise stays the source of truth for time, billing, and financials, while Current owns scheduling and the views your team lives in. Companies, contacts, agreements, opportunities, projects, and time all flow in; the writes you allow flow back.
Before you start
- +A ConnectWise API Member with an API-key pair — not a person's login. Created under System → Members → API Members; the private key is shown exactly once.
- +A clientId from the ConnectWise Developer Network — a free, self-service GUID that ConnectWise requires on every API call.
- +Your site URL (the host you sign in at, like na.myconnectwise.net) and your company ID (the Company field on the ConnectWise login screen).
- +Tenant Admin role in Current — integrations are an admin-only action.
If any of those are missing, work through "Prepare your ConnectWise before onboarding: the setup checklist" first — it walks each one with the exact clicks.
Connect
- 1Open Settings → Integrations → ConnectWise PSAOnly Tenant Admins see this page.
- 2Enter the five credential fieldsSite URL, company ID, public key, private key, and clientId. The first two are not secrets; the last three are, and they're kept server-side only once stored.
- 3Run the test connectionCurrent resolves your instance automatically from ConnectWise's public site-discovery endpoint — there's no API URL to look up — then makes one cheap authenticated read to prove the keys are real before anything is stored. Secrets are encrypted at rest and never sent to the browser again.
- 4Nothing has synced yet — that's deliberateConnecting stores credentials and connection details only. No data is pulled until the first sync runs, so you can connect, review the sync-behaviour switches and board-noise toggles, and pull on your schedule.
- 5Start the initial pullCompanies, contacts, agreements, opportunities, projects, phases, project tickets, members, and time entries come across. Large books take a while; the sync resumes automatically if interrupted.
The 5-minute poll
After the first pull, a delta sync runs every 5 minutes, asking ConnectWise only for records updated since the last pass — ConnectWise timestamps every record, which keeps the polls small and cheap. Pushes (the writes you allow) go out immediately, not on the poll. Current also recognizes its own writes coming back in a poll and skips them, so an edit never ping-pongs between the systems.
Who owns which field
The field-ownership map prevents the two systems from fighting. Current never overwrites a ConnectWise-owned field on push, and ConnectWise pulls never clobber a Current-owned field.
| ConnectWise owns | Current owns |
|---|---|
| Project, ticket, and task names and status | Task start and end dates |
| Hours worked, work roles, agreements, invoicing | Critical-path and milestone flags |
| Time-entry billing and invoice status | Project health (Current Score) |
Disconnecting, and switching PSAs
- +Disconnect lives in the Manage drawer's danger zone and requires typing DISCONNECT — it stops all syncing but deletes nothing already pulled.
- +Projects that were syncing to ConnectWise freeze rather than break: they keep their data, show a clear synced-to-a-disconnected-PSA state, and make no ConnectWise calls until you reconnect.
- +Switching to Autotask is disconnect-then-connect: disconnect ConnectWise here, then connect Autotask from its own card.
- +Switching is free on a fresh workspace, but once you've synced a real book from ConnectWise, connecting Autotask is blocked at connect time so the two providers' records can't collide on their ids — email support@current.day and we'll run a guided migration first.
