Head to head
Current vs HaloPSA
An honest, sourced side-by-side of Current and HaloPSA for MSP project management — where HaloPSA 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 | HaloPSA |
|---|---|---|
| Gantt / timeline view | Yes — native Native Gantt/timeline boards plus a dependency map (@xyflow/react). | Yes — native Native Gantt with inline (right-click) milestone/target-date editing; also List/Calendar/Kanban. |
| Critical-path analysis | Yes — native engine Real native critical-path engine with client-side cycle detection. | Not native / add-on No native critical-path engine; delivered via the third-party Moovila Perfect Project integration. |
| Task dependencies (FS/SS/etc.) | Yes — dependency-aware Dependency-aware scheduling with a dependency graph and cycle detection. | Yes — types not enumerated Native task date dependencies (Q1 2024) shift linked tasks 'based on dependency type'; type set not published. |
| Dependency-aware auto-scheduling | Yes — incl. back-scheduling Dependency-aware scheduling and back-scheduling across timeline, dependency map and what-if scenarios. | Partial — date-shift + AI Dependency date-linking plus AI skills-based auto-scheduling; not a full constraint-based CPM scheduler. |
| Resource management & capacity planning | Availability-driven Availability/PTO-aware scheduling via resource_availability and what-if scenarios; not a multi-year capacity forecaster. | Native + add-on depth Agent Resource Booking and workload dashboards; advanced dispatch boards often via TopLeft/Moovila. |
| PTO / availability-aware scheduling | Yes PTO/availability-aware scheduling and back-scheduling across timeline, dependency map and scenarios. | Calendar-aware AI auto-scheduling factors calendar availability; a dedicated PTO/leave-aware scheduler is not documented as native. |
| Kanban board | Yes — native Native drag-and-drop Kanban (@dnd-kit) for tasks. | Yes — native Native Kanban view for projects/tasks; some partners offer enhanced board add-ons. |
| Milestones | Yes Milestones with scheduling/criticality. | Yes Native milestones editable from the Gantt; surface bottlenecks in real time. |
| Portfolio / multi-project view | Yes Portfolio tiles/views across projects. | Yes Portfolio dashboards/reporting across projects incl. budget and workload. |
| Time tracking | Yes Native time entry that flows to your PSA for billing — Autotask, ConnectWise, or Halo PSA. | Yes Native time tracking with submit-review-approve; only approved time flows to billing. |
| 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 Approved time flows into native billing; invoices auto-generate from contracts; Xero/QuickBooks/Sage sync included. |
| 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. | Portal exposes own invoices Strong self-service portal with granular permissions, but it exposes the customer's own quotes/invoices/contracts rather than isolating all financials. |
| Templates / playbooks | Yes — PMI playbooks PMI/post-merger playbooks and 24 managed-intelligence playbook templates per tenant. | Yes — + AI from SOW Project/ticket templates for any methodology; AI can auto-generate a project from a Statement of Work. |
| Automation / workflow rules | Monitors + notifications Score/monitor engine (run_current_monitor) and notifications; not a general user-built trigger-action rules builder. | Yes — deep Broad workflow engine (creation, status-change, field-change triggers) for routing, SLA, escalations, notifications. |
| Microsoft 365 integration (SharePoint/Teams/Calendar) | Yes — via Graph SharePoint, Teams and Calendar integration via Microsoft Graph. | Strong Teams/email/Entra Strong Teams, O365 email/calendar and Entra ID; native SharePoint project-document integration not documented. |
| AI insights | Yes — Anthropic AI insights powered by Anthropic across the platform. | Yes — extensive AI report insights/forecasts, ticket clustering, MCP endpoint, AI project-from-SOW, skills-based auto-scheduling. |
| Modern UI & architecture (recency of rebuild) | 2026 ground-up rebuild Fully rebuilt/renamed Cascade→Current in 2026 on React 19 + Supabase. | Modern rewrite Current product is a rewrite (~2019 rebrand), Azure-hosted, weekly release cadence with public roadmap. |
| Setup / onboarding effort | Modern self-serve Modern SaaS with transparent per-seat pricing; low-friction adoption alongside your PSA. | Steep + paid onboarding Steep learning curve and a required paid onboarding package (third parties cite ~$4,000 minimum); not turnkey. |
| Pricing model & public price | Transparent — $50/user/mo Public pricing: $50/user/month or $540/user/year. | Public single price + onboarding fee All-inclusive £66/agent/mo (annual), no tiers; a bespoke paid onboarding fee applies on top. |
| 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. | All-inclusive PSA buyers Mid/large MSPs wanting one all-inclusive, highly configurable PSA with projects native to billing. |
Where HaloPSA wins
An all-inclusive single-price PSA where projects live natively next to billing, extreme configurability that bends to almost any workflow, very high user-satisfaction ratings (~4.8/5), a weekly release cadence, and native Gantt/Kanban/milestones with AI project-from-SOW.
Where Current fits: Halo has no native critical-path engine (it leans on the Moovila integration), a steep learning curve, and a required paid onboarding package — it's powerful but not turnkey. Current delivers native critical-path and a DB-isolated partner portal out of the box, adopts faster, and syncs to your PSA — Autotask, ConnectWise, or Halo PSA — for billing rather than asking you to migrate.
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.