Head to head
Current vs ConnectWise
An honest, sourced side-by-side of Current and ConnectWise for MSP project management — where ConnectWise is stronger, and where Current fits.
Written by the Current MSP team · Reviewed by Chad McDonald, Chief Technology Officer (CTO), ITPartners+
Last updated July 18, 2026
YesPartialNo?Not documented
| Capability | Current | ConnectWise |
|---|---|---|
| Gantt / timeline view | Yes — native Native Gantt/timeline boards plus a dependency map (@xyflow/react). | Yes — native Native Gantt (reimagined work plan on the Asio platform) that renders predecessors/dependencies. |
| Critical-path analysis | Yes — native engine Real native critical-path engine with client-side cycle detection. | Not native / add-on Native Gantt does not appear to compute/highlight critical path; CP automation is a Moovila/TopLeft add-on. |
| Task dependencies (FS/SS/etc.) | Yes — dependency-aware Dependency-aware scheduling with a dependency graph and cycle detection. | Yes — types not enumerated Native task predecessors set in the PSA; the specific FS/SS/FF/SF set is not publicly enumerated. |
| Dependency-aware auto-scheduling | Yes — incl. back-scheduling Dependency-aware scheduling and back-scheduling across timeline, dependency map and what-if scenarios. | ?Not documented as native Automatic cascading reschedule not documented as native; automated back-scheduling is a Moovila add-on. |
| Resource management & capacity planning | Availability-driven Availability/PTO-aware scheduling via resource_availability and what-if scenarios; not a multi-year capacity forecaster. | Solid, forecasting weaker Resource assignment by skills/availability and a dispatch portal; forward capacity forecasting less documented. |
| PTO / availability-aware scheduling | Yes PTO/availability-aware scheduling and back-scheduling across timeline, dependency map and scenarios. | ?Not documented Availability factors into dispatch and time-off is tracked; auto-scheduling around approved PTO not documented. |
| Kanban board | Yes — native Native drag-and-drop Kanban (@dnd-kit) for tasks. | Yes — native Ships a native Kanban board for projects in its Asio-native project experience. |
| Milestones | Yes Milestones with scheduling/criticality. | Yes Native milestones with milestone triggers and milestone-based billing. |
| Portfolio / multi-project view | Yes Portfolio tiles/views across projects. | Dashboards/reports Cross-project visibility via dashboards and custom reports rather than a portfolio Gantt/roadmap. |
| Time tracking | Yes Native time entry that flows to your PSA for billing — Autotask, ConnectWise, or Halo PSA. | Yes (UX complaint) Native billable time entry to invoicing; time-entry usability is a common review complaint. |
| Billing / PSA integration & source-of-truth | Syncs to PSA or native 'autotask_synced' keeps Autotask as billing source of truth (Current owns scheduling); or fully Current-native. Also integrates ConnectWise and Halo PSA. | Yes — is the PSA Native automated project/milestone billing; project time bills in the same platform, no external sync. |
| Client / partner portal (with financial isolation) | Yes — DB-level isolation Partner portal with genuine DB-level financial isolation (RLS + partner-safe views + restrictive policies); partners never see financial data. | Config-dependent Native portal surfaces invoices/balances to clients; a finance-isolated view depends on portal configuration. |
| Templates / playbooks | Yes — PMI playbooks PMI/post-merger playbooks and 24 managed-intelligence playbook templates per tenant. | Yes Pre-built and custom project templates to standardize repeatable work. |
| Automation / workflow rules | Monitors + notifications Score/monitor engine (run_current_monitor) and notifications; not a general user-built trigger-action rules builder. | Yes — mature Deep business-wide workflow engine; delegates projects/tasks via milestone triggers; Asio adds RPA. |
| Microsoft 365 integration (SharePoint/Teams/Calendar) | Yes — via Graph SharePoint, Teams and Calendar integration via Microsoft Graph. | Teams + calendar Teams via Sidekick and calendar sync; SharePoint document tie-ins generally via third-party connectors. |
| AI insights | Yes — Anthropic AI insights powered by Anthropic across the platform. | Ticket-centric Sidekick AI (classification, summaries, resolutions, sentiment) in Teams; no documented project-management AI. |
| Modern UI & architecture (recency of rebuild) | 2026 ground-up rebuild Fully rebuilt/renamed Cascade→Current in 2026 on React 19 + Supabase. | Rebuild in progress Legacy Manage UI criticized as clunky; modern 'PSA powered by Asio' rolling out since mid-2025. |
| Setup / onboarding effort | Modern self-serve Modern SaaS with transparent per-seat pricing; low-friction adoption alongside your PSA. | High effort Steep learning curve (weeks of training); implementation commonly runs from hundreds to $20,000+ (third-party). |
| Pricing model & public price | Transparent — $50/user/mo Public pricing: $50/user/month or $540/user/year. | Quote-based, no public price No public price; third-party estimates ~$35-$65+/user/mo (some cite $60-85); implementation extra. |
| Best-fit user | Modern delivery + partner isolation MSPs wanting purpose-built dependency-aware/critical-path delivery, a financially-isolated partner portal, and billing sync to their PSA — Autotask, ConnectWise, or Halo PSA. | Consolidating MSPs Mid/enterprise MSPs consolidating ticketing+time+billing+CRM+projects into one PSA and willing to invest in config. |
Where ConnectWise wins
All-in-one PSA breadth (ticketing, procurement, CRM, billing, projects in one system of record), a very large integration marketplace (several hundred partners), a mature business-wide workflow engine, and — with the Asio rebuild — native Gantt and native project Kanban.
Where Current fits: Breadth is not the same as depth in project delivery: critical-path automation still requires add-ons (Moovila/TopLeft), the legacy UI is still being migrated, and onboarding is heavy. Current integrates with ConnectWise (shipped 2026-07-18) — as it does with Autotask and Halo PSA — so you can keep your PSA for billing and run delivery in a purpose-built, dependency-aware tool.
Why MSPs choose Current
- A modern 2026 ground-up rebuild (React 19 + Supabase), not a project module bolted onto a decades-old help-desk or PSA core — so the delivery experience is fast and purpose-built rather than layered onto legacy screens.
- A real, native critical-path engine plus dependency-aware scheduling and back-scheduling — native to the product, not a paid Moovila/TopLeft add-on the way it is for Autotask, ConnectWise and HaloPSA.
- PTO/availability-aware scheduling that runs consistently across the timeline, the dependency map AND what-if scenarios — availability-aware planning most incumbents only partially document.
- Kanban AND Gantt AND an interactive dependency map all native in one tool (Autotask lacks native project Kanban; Syncro lacks project boards entirely).
- A partner portal with genuine database-level financial isolation — Postgres RLS + partner-safe views + restrictive policies — so partners can never see financial data. Incumbent portals (Autotask, ConnectWise, Syncro, Halo) are designed to EXPOSE invoices to clients; Current is the opposite by construction.
- Flexible source-of-truth: 'autotask_synced' keeps Autotask as the billing record while Current owns scheduling, or 'current-native' where Current is the source of truth — plus shipped ConnectWise and Halo PSA integrations and Datto/Addigy/ScalePad connectors.
This is the two-tool view. See the full msp project management software, compared for all 7 tools side by side.