What is a PSA overlay, and should an MSP keep its PSA?

A PSA overlay is software that runs on top of your professional services automation tool, syncs records with it in both directions, and adds capabilities the PSA does not have, such as critical-path project scheduling, a modern CRM, AI-written business reviews or a customer portal. The PSA stays the system of record for time, billing and contracts. When your PSA bills correctly, keeping it and adding an overlay is lower risk than a migration. Current works as a PSA overlay on Autotask, ConnectWise, HaloPSA, Syncro, Rev.io and SuperOps, and it can also run with no PSA at all. If you are new to the terms, start with the difference between a PSA and a CRM.

What a PSA overlay is, and what it is not

Three kinds of tools get called add-ons to a PSA, and only one is an overlay in the sense that matters for a buying decision:

• Reporting tools read from the PSA and draw charts. Nothing goes back, so they cannot change how work is done.
• Point add-ons fix one gap, such as a dispatch board, a quoting tool or a client portal, and may write back for that one job. CloudRadial, for example, describes its portal as a white-labeled client experience layer on top of your PSA.
• An overlay syncs the core records (companies, contacts, projects, tasks, time, opportunities) two-way, so your team can work in the overlay day to day while the PSA keeps billing, contracts and the financial history.

An overlay is not a second PSA. If both systems try to own invoices, contracts and time, you get two sources of truth and an accounting reconciliation every month. A well-built overlay draws a clear line: the PSA owns money, the overlay owns the work it adds.

Why MSPs keep their PSA

• Billing works. Contracts, recurring services, invoicing and the accounting export are tuned over years. Rebuilding that is the riskiest part of any PSA migration.
• History lives there. Tickets, time and contract changes going back years are what your finance team and your auditors rely on.
• Integrations depend on it. Your RMM, quoting, documentation and distributor tools are wired to the PSA.
• People know it. Technicians and billing staff are trained on the PSA's workflows.

What a PSA tends not to do well is the work around those records: dependency-aware scheduling, a sales pipeline your account managers like using, a business review a customer wants to read, and a portal you can show a customer without exposing money. That is the gap an overlay targets.

When to replace the PSA instead

An overlay does not fix a PSA problem that sits in billing or contracts. Replace the PSA when:

• Invoices are wrong or need manual rework every month, and the cause is the PSA's contract model.
• The vendor's pricing or support has become a reason in itself to leave.
• You are merging with another MSP on a different PSA and need one billing system.
• Your current PSA cannot connect to the tools you have standardized on.

Even then, an overlay can make the move easier: if your team already works in the overlay, moving the billing system underneath it changes less for them. For project work specifically, see Autotask Projects alternatives and ConnectWise project management alternatives.

What to check before you buy a PSA overlay

• Which records sync both ways, and which only come in. Ask per object: companies, contacts, projects, tasks, time, opportunities, notes.
• Who owns which fields. Billing fields should stay with the PSA; scheduling fields (start and end dates, critical path) can belong to the overlay.
• Time entry. Can a technician enter time in the overlay, and is it guaranteed to reach PSA billing? A time entry that cannot sync should be refused at entry, not discovered at month end.
• Write safety. How does the overlay stop a test from writing to your live PSA?
• What happens on disconnect. Your data should stay, and nothing should keep calling the old PSA.
• Customer visibility. If the overlay has a customer portal, can a customer ever see a cost or margin figure?

How Current works as a PSA overlay

Current connects to one PSA per workspace, a rule enforced in the database so every synced record has exactly one external identity. The PSA choice decides what syncs:

• Autotask, ConnectWise PSA and HaloPSA: deep two-way sync of companies, contacts, opportunities, projects, tickets, contracts and time. The PSA stays the source of truth for time and billing; Current owns scheduling.
• Syncro: two-way sync of customers, contacts, leads, tickets, estimates, contracts and time, with projects as parent tickets you choose to track.
• Rev.io: two-way sync of customers, contacts, notes, projects and time, with tickets, agreements, invoices, opportunities and quotes read in. Added October 2026, with a few behaviours still being confirmed against a live account.
• SuperOps: supported customer, contact, ticket and time changes sync both ways, and billing records are read after you confirm the currency. Projects and opportunities stay in Current. Live account validation is still pending.

What Current adds on top

• Projects with dependency-aware scheduling, a critical path, Kanban and Gantt views, and PTO-aware timelines. See MSP project management.
• Time entry that flows to the PSA for billing, guarded so a time entry that cannot sync is never created.
• A CRM with pipelines, campaigns, website lead forms, commissions and whitespace analysis that maps what each customer buys against what you sell.
• AI-written business reviews and a standing roadmap per customer, fed by your PSA, RMM, security, backup and lifecycle tools.
• A customer portal where people you invite see project status, timelines and shared documents, with financial data blocked at the database layer.
• Dashboards and scheduled reports across delivery, team, finance and sales.

Guardrails on the sync

• A project can be PSA-synced or Current-native. A Current-native project never triggers a PSA call.
• Two-way sync can be turned off per workspace in Integrations, so Current reads without writing back.
• CRM writes to the PSA are guarded by a test mode that only writes to companies with a test prefix until you go live.
• Disconnecting a PSA stops all syncing and deletes nothing. Synced projects freeze with their data and make no further calls.

Running with no PSA

A workspace can start with no PSA: native projects, scheduling, time entry, the CRM and campaigns all work, and features that need PSA billing data show a connect-your-PSA state until you add one. That makes Current usable for internal projects or a new MSP, and connecting a PSA later runs the same mapping and first sync.

A week with an overlay, in practice

Take a fictional 25-person MSP, Northgate IT, on Autotask. Its billing team keeps working in Autotask exactly as before. Its project managers plan in the overlay: a firewall replacement for a customer has eight tasks, and when the vendor ships the hardware a week late, the overlay moves every dependent task and shows the new go-live date. Technicians enter time against those tasks in the overlay, and each entry lands in Autotask against the right project for invoicing.

Its account managers work their pipeline in the overlay's CRM, and won opportunities appear in Autotask. At the end of the quarter the overlay drafts each top customer's business review from Autotask tickets and contracts plus the RMM and backup feeds, and the customer approves two roadmap items in the meeting. Nobody re-keys anything, and the month-end invoice run is unchanged.

Common objections

"Two systems means two places to look"

Only if both systems try to do the same job. Decide up front which roles work where: billing in the PSA, projects, pipeline and reviews in the overlay. Technicians who log time in the overlay do not need to open the PSA for that work.

"Sync breaks"

Ask how the overlay reports a sync problem and who hears about it. A sync that fails silently is the real risk. Look for per-record sync status, an alert to an admin when the PSA refuses a request, and a test mode for writes.

"It is one more bill"

Compare it to what the overlay replaces: a separate project add-on, a CRM, a QBR tool and a portal can be four contracts. Price the stack you would retire, not the overlay alone, and include the hours your team spends moving data between those tools each month.

So, should you keep your PSA?

If billing is right and the pain is in scheduling, selling, reviewing or showing work to customers, keep the PSA and add an overlay. If billing itself is the problem, plan a PSA change, and consider whether an overlay can carry your team through it. Current is priced per user with AI included; see pricing and the comparison pages for side-by-side detail.