Current + Syncro integration

Syncro became Current's fourth PSA in September 2026, at the same depth as Autotask, ConnectWise and HaloPSA: customers, tickets and time in both directions, not a one-way import. Syncro stays your system of record for tickets, invoicing and contracts, 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

Syncro has no project record, so a project in Syncro is a parent ticket with child tickets under it. Current works in that shape rather than around it: deploy a project from Current and you get a parent ticket plus a child ticket for each task, with start dates, due dates, status and assignee kept in step both ways. Time logged in Current lands as a Syncro ticket timer entry against a Labor product, so billing stays where it belongs. Projects that do not belong in the PSA run Current-native and never make a Syncro API call.

What data flows

• Customers and contacts, kept in step with Current's CRM so your book of business matches Syncro.
• Sales Leads become deals, with your own stage map. Syncro's inbound email queue stays out of the CRM: a Lead reaches Current only when it carries a sales status or a dollar amount.
• Parent and child tickets become projects and tasks, in both directions, with last-editor-wins arbitration on the shared fields.
• Scheduling: Current pushes start dates, due dates and status back, so Syncro reflects the real plan.
• Time entries: time logged in Current flows to Syncro for billing, and invoiced time is never touched again.
• Contracts and recurring invoice schedules drive each company's MRR, priced per line on that line's own cadence.
• Estimates become quotes on the company record, and an approved estimate becomes a won quote ready to convert.
• Appointments become busy days, and the ones typed as time off become time off the scheduler works around.
• Syncro's RMM half, read-only: assets, patches, installed applications and alerts feed the whitespace and posture views.

Why it matters

A Syncro shop already has one system for monitoring, tickets and invoicing, which is most of why they chose it. What it has never had is a plan: parent and child tickets carry a status each, so nothing answers which task is driving the finish date, or what a three-day slip does to it. Current adds that layer and leaves the rest of Syncro alone.

Projects are opt-in, on purpose

Plenty of Syncro shops use parent and child tickets for grouping that has nothing to do with project work, so Current never turns every parent ticket into a project. It tracks the ones it created, plus the ones an admin picks from a list on the Syncro card. There is an optional rule that adopts new parent tickets carrying a particular issue type, and it is off until you turn it on. A parent ticket you have not tracked stays an ordinary service ticket everywhere in Current.

Which system owns what

Syncro remains the source of truth for time, billing, invoicing and contracts. Current owns scheduling, dependencies, the critical path, phases and milestones, which Syncro does not have, and pushes the resulting dates back. Company notes stay in Current rather than being appended into the single free-text field on a Syncro customer, and nothing Current does can change a customer's invoice, a rate or an asset.

Two things to know

Syncro has no feedback API, so CSAT in Current comes from CrewHu rather than Syncro. And a Syncro timer bills at the rate on its Labor product, so every time entry needs one; the technician picks it when logging time.

Won estimates become projects

An approved Syncro estimate lands in the same won-quote queue as ScalePad Quoter, ConnectWise CPQ, Kaseya Quote Manager and HaloPSA wins, and the same wizard turns it into a project, a ticket or a contract task with charges on the parent ticket. A Syncro estimate line carries a product, not a recurring or labour flag. Map your product categories once and every estimate after that sorts itself into monthly, one-time and hours.

Push is a setting

Writing back to Syncro is gated. Two-way sync controls project and task pushes, and CRM write mode starts off, with a test mode in between that only touches companies named for testing. An evaluation is read-only until you decide otherwise.

Getting set up

You need a Syncro API token created as a dedicated user whose security group can read the areas above and edit tickets, with parent and child tickets switched on for the account. The connection test proves the token before anything is stored. One PSA per workspace.