Current + Halo PSA integration

Current added Halo PSA as a first-class two-way sync in July 2026, alongside its Autotask and ConnectWise integrations. Halo PSA stays your billing system of record — companies, contracts, tickets, and financials — while Current adds the delivery layer on top: dependency-aware scheduling, a native critical-path engine, Kanban and Gantt boards, milestones, and a partner portal with database-level financial isolation. One PSA connects per workspace.

What the integration does

Projects synced to Halo PSA keep Halo authoritative for billing and financials while Current owns scheduling — start and end dates, task criticality, dependencies, and milestones. Time entered against those projects flows back to Halo so your billing records stay complete and accurate. Projects that don't belong in the PSA run Current-native and never make a Halo API call, which is ideal for internal or cross-department work you'd never bill through Halo.

What data flows

• Companies and contacts — kept in step with Current's CRM so your book of business matches Halo.
• Projects, phases, and tickets/tasks — created and updated in both directions, with last-editor-wins arbitration on the two-way fields.
• Scheduling — Current pushes start dates, end dates, and milestones back to Halo so the PSA reflects the real plan.
• Time entries — native time logged in Current flows to Halo for billing.
• Money fields — normalized on the way in so amounts read consistently between systems.

Why it matters

HaloPSA is billing-native and has native milestones, but modern critical-path scheduling — PTO- and availability-aware planning, back-scheduling, an interactive dependency map, and a real cycle-detecting engine — isn't its focus. Current supplies that delivery layer and a unified CRM, then keeps Halo authoritative for the money. You get modern project delivery without leaving the PSA your billing and contracts already run on.

Because Halo PSA support is new as of July 2026, it works the same way as Current's Autotask and ConnectWise syncs: the two-way push is gated by a tenant setting so you control when Current writes back, and Current-native projects are guarded to never make a stray API call to your live Halo instance.

Which system owns what

HaloPSA remains the billing system of record while Current owns scheduling and pushes the resulting dates back. Projects, milestones, tasks, opportunities, and time entries sync both ways; clients, contacts, tickets, and contracts flow in from Halo. Time logged in Current reaches Halo for billing, and won Halo quotes walk into projects through the same engine that handles other quoting tools.

One honest caveat about contract detail

Worth knowing before you evaluate coverage features. Where a Halo contract exposes line-level detail, Current reads those lines and matches them to your offerings normally. Where a contract exposes no line detail, Current falls back to a single synthetic line derived from the period charge, and that synthetic line will not match specific offering patterns. The practical effect is that coverage accuracy on Halo depends on how your contracts are structured, and contracts without line detail will read as thinner than they are.

Push is a setting

Writing back to Halo is a tenant setting that starts off, so an evaluation is read-only until you decide otherwise.

Getting set up

You need a HaloPSA API application with access to the entities above. HaloPSA support shipped in July 2026 and is a first-class integration alongside Autotask and ConnectWise, not a partial one. One PSA per workspace.