Autotask, ConnectWise, HaloPSA, Syncro, Rev.io, or SuperOps: choosing your PSA
The wizard's PSA step, the one-PSA-per-workspace rule, switching later, and what Current-only mode means.
On this page · 4 sections
Current runs on the PSA you already run. The setup wizard's PSA step asks one question, Autotask, ConnectWise PSA, HaloPSA, Syncro, Rev.io, SuperOps, or no PSA at all, and everything after it follows that choice: what syncs, the mapping step, the first pull, even field labels like work role versus billing code.
The choices
| Choice | What it means |
|---|---|
| ConnectWise PSA | Deep two-way sync: companies, contacts, agreements, opportunities, projects, project tickets, members, and time. ConnectWise stays the source of truth for time and billing; Current owns scheduling. |
| Autotask | The same depth against Autotask, the sync Current launched with. Autotask stays the source of truth for time and billing; Current owns scheduling. |
| HaloPSA | The same depth against HaloPSA, clients, contacts, opportunities, projects, milestones, tickets, contracts, and time. Halo stays the source of truth for time and billing; Current owns scheduling. Added July 2026. |
| Syncro | Two-way sync of customers, contacts, leads, tickets, estimates, contracts and time. Projects are parent tickets with child tickets under them, and you choose which ones Current tracks. Syncro stays the source of truth for time and billing; Current owns scheduling. Added September 2026. |
| Rev.io | Two-way sync of customers, contacts, notes, projects and time with the Rev.io PSA, ticket status changes sent back, plus tickets, agreements, invoices, opportunities and quotes read in. Opportunities and quotes are read-only for now. Rev.io stays the source of truth for time and billing; Current owns scheduling. Added October 2026, and a few behaviours are still being confirmed against a live Rev.io account. |
| SuperOps | Supported customer, contact, ticket and time changes sync both ways, with billing records read after you confirm the currency. Enable the RMM feed with the same credentials. Projects and opportunities stay in Current. Live account validation is still pending. |
| We don't use a PSA | Current runs standalone: native projects, the CRM, campaigns, scheduling, and time entry all work with no PSA. Connect one later whenever you're ready. |
One PSA per workspace
A workspace syncs one PSA at a time, enforced in the database, not just the interface. The reason is record identity: every synced record carries exactly one external identity, so there is never a question of which system a company, project, or time entry belongs to. Whichever PSA you pick, the other five cards in Integrations show a "disconnect first" state instead of a connect form.
Switching later
- 1Disconnect the current PSAIntegrations → the connected PSA's Manage drawer → danger zone. It's a typed confirmation, it stops all syncing, and it deletes nothing already pulled.
- 2What happens to synced projectsThey freeze rather than break: a project synced to a disconnected PSA keeps its data, shows a clear frozen-sync state, and makes no calls to the old provider. It doesn't re-attach to the new PSA.
- 3Connect another PSAFrom its own card, with its own credentials. New pulls build your book from the new provider. See the connect article for the one you're joining.
Switching is free while a workspace is still fresh, but once you've synced a real book from one PSA, connecting a different one is blocked at connect time so the two providers' records can't collide, email support@current.day and we'll run a guided migration first.
What Current-only mode means
- Projects are Current-native: dependency-aware scheduling, critical path, Kanban, Gantt, and time entry are all fully functional, with Current as the source of truth.
- The CRM works standalone: companies, contacts, opportunities, campaigns, sequences, and booking links.
- Features that read PSA billing (the whitespace grid, MRR, agreement-driven customer status) show a connect-your-PSA state instead of empty charts, so nothing looks broken; they light up the day you connect one.
- Starting with no PSA is not a commitment, connect Autotask, ConnectWise, HaloPSA, Syncro, Rev.io, or SuperOps later and the wizard's mapping and first-sync steps run from Integrations instead.
For the connection walkthroughs, see "Connect Autotask and choose what syncs", "Connect ConnectWise PSA and choose what syncs", "Connect HaloPSA and choose what syncs", "Connect Syncro and choose what syncs", "Connect Rev.io and choose what syncs", and "Connect SuperOps to Current".