Skip to content
Current/ Help Center

Connect ConnectWise PSA and choose what syncs

3 min read · Updated Jul 21, 2026

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.

Note
One PSA per workspace
Current syncs one PSA at a time — ConnectWise PSA, Autotask, or HaloPSA, chosen at signup and switchable later. If another PSA is connected, the ConnectWise card asks you to disconnect it first; the rule is enforced in the database, not just the interface. See "Autotask, ConnectWise, or HaloPSA: choosing your PSA in Current".

Before you start

SCREENSHOT — coming soon
The ConnectWise PSA card on Integrations: connection status, last-sync time, and the Manage button.
  • 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

  1. 1
    Open Settings → Integrations → ConnectWise PSA
    Only Tenant Admins see this page.
  2. 2
    Enter the five credential fields
    Site 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.
  3. 3
    Run the test connection
    Current 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.
  4. 4
    Nothing has synced yet — that's deliberate
    Connecting 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.
  5. 5
    Start the initial pull
    Companies, contacts, agreements, opportunities, projects, phases, project tickets, members, and time entries come across. Large books take a while; the sync resumes automatically if interrupted.
Note
New workspaces: the wizard does this for you
In the setup wizard, the PSA step carries the same credential form, followed by a mapping step — board noise and won-quote stages — before the first pull. See "Autotask, ConnectWise, or HaloPSA: choosing your PSA in Current" and "Your first 15 minutes: the setup wizard".

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 ownsCurrent owns
Project, ticket, and task names and statusTask start and end dates
Hours worked, work roles, agreements, invoicingCritical-path and milestone flags
Time-entry billing and invoice statusProject health (Current Score)
Note
Resync, connection health, and rotating keys
A few ConnectWise operations are worth calling out. The project Resync button and "pull tasks" pull a single project's tasks on demand — handy after adding a project directly in ConnectWise. The connection-health card is honest about areas your API keys can't reach: instead of showing a green zero as if nothing were there, it names the missing permission — for example "grant Time read" — so you know to widen the API Member's security role rather than chase a phantom sync problem. Service boards beyond the first 25 map correctly, so a board low on the list isn't skipped. And rotating your ConnectWise API keys — pasting a fresh key pair over the old one — is accepted rather than wrongly blocked as a duplicate connection.

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.
Heads up
Reading is the default — writing is gated
Pulling from ConnectWise is always on once connected. Writing back is gated twice: the two-way sync switch in the Manage drawer controls task-field pushes, and CRM write mode (off by default, with a test mode in the middle) controls every CRM write. Nothing writes to your ConnectWise until you deliberately open those gates. See "What Current writes back to ConnectWise (and when)".
Was this helpful?