Current + ConnectWise PSA integration

Current supports ConnectWise PSA as a first-class two-way sync, the same way it supports Autotask and Halo PSA. You keep ConnectWise as your billing and ticketing source of truth, and Current adds the delivery layer ConnectWise's project module has historically leaned on add-ons to provide: a native critical-path engine, dependency-aware scheduling, Kanban and Gantt boards, milestones, and a financially-isolated partner portal. One PSA connects per workspace.

What the integration does

Projects synced to ConnectWise keep the PSA authoritative for billing and financials while Current owns scheduling — dates, criticality, dependencies, and milestones. Native time entered in Current flows back so billing stays complete. Projects that don't belong in the PSA can run Current-native and never make a ConnectWise API call, which is ideal for internal work.

What data flows

• Projects, phases, and tickets/tasks — two-way, with two-way parity modes so updates on either side reconcile cleanly.
• Scheduling — Current pushes the plan back to ConnectWise so the PSA reflects real start dates, end dates, and milestones.
• Time entries — native time logged in Current flows to ConnectWise for billing.
• Money fields — normalized on the way in so amounts read consistently between systems.
• Companies and contacts — kept in step with Current's CRM.

ConnectWise CPQ

Current bridges ConnectWise CPQ (formerly Sell), so quoting and the deal record stay connected for ConnectWise-stack shops. That keeps sales-to-delivery handoff tight without re-keying quote data by hand.

RMM evidence for SBRs

ConnectWise RMM feeds view-only evidence into Current's SBR/QBR module, so patch, device, and health data can back up the story you tell partners in a strategic business review. That data is read-only and never customer-facing by vendor name — it becomes proof points in the review, not raw tool output.

Why it matters

ConnectWise is mature and billing-native, and its Asio rebuild is modernizing the classic UI. But native critical-path scheduling has typically meant a Moovila or TopLeft add-on, and ConnectWise's own in-stack CRM and CPQ don't reach across to other PSAs. Current gives you a modern, unified delivery-and-CRM layer that syncs to ConnectWise rather than replacing it — one transparent price, every feature included.

Which system owns what

ConnectWise stays the system of record for time, agreements, and billing. Current owns scheduling. The same entity set flows as with the other supported PSAs: projects, phases, tickets, tasks, and time entries pull in, while task dates, project creation, and time entries push back. The dependency graph stays in Current, because ConnectWise has no field to receive the richer relationship types.

• Two-way sync covers companies, contacts, opportunities, projects, service tickets, and time entries.
• ConnectWise CPQ won quotes walk into projects through the same win-quote engine used for other quoting tools.
• A view-only ConnectWise RMM feed supplies fleet evidence for business reviews.

Push is a setting, and starts off

As with every PSA Current supports, writing back to ConnectWise is a tenant setting. Leave it off and Current is read-only against your PSA, which makes a trial genuinely low-risk: you can run real projects on real data and know with certainty that nothing has been written to ConnectWise.

A note on the Asio migration

ConnectWise is mid-migration to its Asio platform, so the project experience is changing. That is worth factoring into any decision about where your scheduling lives. Running delivery in Current insulates you from that churn somewhat, since your plans, dependencies, and history stay put regardless of which ConnectWise interface you are looking at that quarter.

Getting set up

You need ConnectWise API member credentials with access to the entities above. Current measures actual access at connection time rather than trusting the reported permission list, so a missing permission surfaces immediately. One PSA per workspace.