Try it on your HaloPSA data and decide what is written back
Connecting on its own changes nothing in Halo.
For the free trial: card up front. We email you the exact amount three days before the first charge, and you can cancel anytime during the trial.
What does Current add to HaloPSA?
Current is a CRM and project delivery platform that runs on top of HaloPSA instead of replacing it. It reads your Halo clients, contracts, opportunities, projects, tickets and time, then adds pipeline, dependency-aware scheduling, business reviews and dashboards, and writes the work your team allows back to Halo.
The PSA stays the system of record. It just stops being the place everyone has to live all day.
What syncs with HaloPSA
Each row is a HaloPSA record type, which way it moves, and who wins when both sides change it.
| HaloPSA record | Direction | What moves |
|---|---|---|
| Clients | DirectionTwo-way | What movesPulled into Current with their sites. Halo's account manager fills Current's, and a company you push from Current carries its account manager. |
| Contacts (users) | DirectionTwo-way | What movesPulled into Current. Saving a contact in Current sends its name, email, phones, title and site to Halo. |
| Opportunities | DirectionTwo-way | What movesHalo opportunities sit in your Current pipeline, and stage moves go both ways. |
| Projects, milestones and tasks | DirectionTwo-way | What movesHalo owns project completion and its own rollups. Current owns scheduling: task dates, dependencies and the critical path. |
| Tickets | DirectionRead into Current | What movesEach client's tickets fill the company page, reports and business reviews. A ticket in a Resolved-type status counts as closed. |
| Time entries | DirectionTwo-way | What movesTime logged in Current goes to Halo with the charge rate and contract you picked; time logged in Halo comes back to Current. |
| Contracts | DirectionRead into Current | What movesMonthly recurring revenue is read from the recurring invoices behind each contract. Never written. |
| Invoices | DirectionRead into Current | What movesCurrent shows whether time has been invoiced, and never creates, posts or voids a Halo invoice. |
| Feedback (CSAT) | DirectionRead into Current | What movesHalo's own survey scores feed company health and business reviews. A tenant admin can turn this off. |
| Agents, holidays and time off | DirectionRead into Current | What movesAgents are matched to Current users by email, and the scheduler skips holidays and time off. |
What HaloPSA stays in charge of
HaloPSA stays the source of truth for tickets, time, billing and financials. Current works on top of it and never replaces it.
Connect HaloPSA in 4 steps
A tenant admin connects HaloPSA once, from Settings, Integrations, with a Halo administrator login at hand.
Step 1: Authorise a new API application
In Halo, go to Configuration, Integrations, Halo API, and choose Authorise a new application. For the Authentication Method, pick Client ID and Secret (Services), the flow meant for a background integration with no person signing in.
Step 2: Copy the Client ID and Client Secret
Halo shows a Client ID and generates a Client Secret for the application. Keep both in a password manager.
Step 3: Grant the permissions
On the application's Permissions tab, grant the areas the sync needs. If you are unsure, Halo's guidance is to set the scope to all. Back the application with an agent whose role can do everything the sync reads and writes, because Halo limits an application by its agent's permissions too.
Step 4: Connect in Current and start the first pull
Open Settings, Integrations, HaloPSA, and enter your Halo instance URL, Client ID and Client Secret (and the Tenant value on hosted Halo, if it asks for one). Run the test, then start the first pull.
Connect HaloPSA in your trial
For the free trial: card up front. We email you the exact amount three days before the first charge, and you can cancel anytime during the trial.
What you get on day one with your HaloPSA data
Start a trial, connect HaloPSA, and these modules fill from the records it already holds. Every module is included in the seat: one module or all of them, same price.
Sell
CRM + pipeline, Whitespace, Campaigns + sequences, Commissions
Deliver
Projects, Roadmaps, Time + timesheets
Support
Client portal
Run the business
Billing + finance
Grow accounts
QBR + SBR, Customer success, Dashboards, Reporting
The Service Desk and Dispatch are in Beta and switched on for a workspace by Current's team on request.
Quoting tools that work with HaloPSA
Won quotes land in Current's Won quotes list, and a wizard turns each into a Halo project with its charges.
- HaloPSA quotes: Halo's own quotes join the same Won quotes list as other quoting tools. The wizard builds the project and pushes the charges into Halo.
Limits of the HaloPSA connection
What to know before you connect.
- There is no live per-ticket detail read from Halo. A ticket drawer shows the ticket Current already has from the sync.
- Halo publishes no task picklists (task type, department, priority) over its API, so those stay in Current.
- Halo has no single changed-since filter across every record, so for some records Current compares what it last saw. It paces itself against Halo's rate limit of 700 requests every 5 minutes, which makes it slower to notice some changes than on Autotask or ConnectWise.
- An under-scoped application returns empty data rather than an error, so check the scope and the agent's role if an area looks empty.
The questions MSPs ask first.
Does Current replace HaloPSA?+−
No. Current is not a PSA. Halo keeps tickets, contracts, time and billing, and Current adds the CRM, dependency-aware project scheduling, business reviews and dashboards on top, with a two-way sync between the two.
Does Current write to HaloPSA billing?+−
No invoices and no contracts. Contracts, the product catalog and invoices are read only. Current writes time entries with the charge rate and contract you picked, and the charges of a won quote you convert.
What do I need to connect HaloPSA?+−
A Halo API application with the Authentication Method Client ID and Secret (Services), its scope set to the areas the sync needs (Halo suggests all), an agent whose role covers what the sync reads and writes, and your Halo instance URL.
Can I run critical path scheduling on HaloPSA projects?+−
Yes, in Current. On a synced Halo project Current owns the scheduling: task dates, dependencies and the critical path. Halo keeps project completion and its own rollups.
Does Current work with on-premise HaloPSA?+−
Yes. Enter your own host as the instance URL, such as support.yourcompany.com. Hosted Halo uses an address like yourcompany.halopsa.com and the Tenant value from Halo's API Details.
Where does Current read HaloPSA contract revenue from?+−
From the recurring invoices behind each contract. Each line is turned into a monthly figure, and the contract itself is never written.
How often does Current sync with HaloPSA?+−
Every 5 minutes, paced against Halo's rate limit of 700 requests every 5 minutes. The writes you allow go out as they happen.
See Current on a real book of business.
The demo walks through the pipeline, the dependency engine, the AI briefs, and how time flows straight into your PSA billing.