Syncro sync: the complete field-mapping reference

10 min read · Updated Sep 17, 2026

This is the reference for what moves between Syncro and Current, which direction it moves in, and who wins when both sides change. Current's rule everywhere is that the PSA owns money and record identity, and Current owns scheduling. Where a field exists on both sides and both may edit it, the most recent edit wins.

Customers

Syncro	Current	Direction
Customer id	Company external id	In, and set on create
Business name, or first and last name for a residential customer	Company name	Both ways
Email, phone, address	Company contact details	Both ways
Custom fields (properties)	Company custom fields	Both ways, per field
Notes (the single text field)	Not read	Neither

Syncro customers can be a business or an individual, so a residential customer's name is built from the first and last name instead of a business name. Syncro has no account-manager field, which means a company's owner in Current is whatever your team set there and a sync never touches it.

Contacts

Syncro	Current	Direction
Contact id	Contact external id	In, and set on create
Name (one field)	First and last name	Both ways, split on the first space going out
Email, phone, mobile	Email, phone, mobile	Both ways
Title	Title	Both ways
No equivalent	Active or inactive	Current only. Deactivating in Current is not written to Syncro.

Leads and deals

Syncro Leads serve two purposes: sales opportunities and the inbound email queue. Only the sales ones become deals. A Lead reaches the CRM when its status is Opportunity, Prospect, Waiting on Client, In Negotiation, Pending, Won or Lost, or when its opportunity amount is above zero.

Syncro	Current	Direction
Lead status	Pipeline stage, through the stage map on the Syncro card	Both ways
Won or Lost	Deal won or lost, with the close recorded as a sync close	In
Opportunity amount	One-time amount	Both ways
Likelihood	Probability	Both ways when it reads as a percentage
Owner	Deal owner, matched by the user's email	Both ways when the person exists on both sides
No equivalent	Monthly recurring amount, win and loss reasons, lead source	Current only

Note

A lead that leaves the gate keeps its deal

If someone moves a Lead back to New or clears its amount, the deal in Current stays exactly as it is, with its stage, its activity and any commission history. Current does not delete it and does not mark it lost, because a machine close would be a commission decision nobody made. It simply stops updating.

Projects: parent and child tickets

Syncro has no project record, so a Current project is a parent ticket and its tasks are the child tickets under it. Current tracks a parent ticket when it created it, or when an admin adopted it from the Syncro card. Syncro nests exactly one level, so a child ticket can never itself be a parent.

Syncro	Current	Direction
Parent ticket subject	Project name	Both ways
Parent ticket due date	Project end date	Both ways
Parent ticket status	Project status	In
Child ticket subject	Task name	Both ways
Child ticket start date and due date	Task start and end dates	Both ways
Child ticket status	Task status	Both ways
Child ticket assignee	Task assignee, primary only	Both ways
Child ticket number	Task reference number	In
Priority	Priority order, set when the task first arrives	In
No equivalent	Phases, dependencies, critical path, milestones, estimated hours, percent complete	Current only

Because Syncro has no phase, Current puts a project's tasks in one container named Tasks so the board and the Gantt have something to group by. That container exists in Current only and is never written to Syncro.

Time entries

Syncro	Current	Direction
Ticket timer entry id	Time entry external id	Set on push, read back after
Start and end time	Date and hours	Out on push, in on the mirror
User	The person who logged it, matched by email	Both ways
Notes	Summary	Out
Product (a Labor product)	Billing code	Out
Billing status: non-billable, unbilled, billed, invoiced	Billable flag and approval state	In
No equivalent	Internal notes, contract, role	Current only. Internal notes never leave Current.

Once Syncro marks a timer entry invoiced it is immutable, and Current treats it that way: the entry is marked approved and posted in Current and no further write is attempted. Time logged against a ticket that is not part of a tracked project is mirrored for reporting but is not project time.

Contracts, recurring invoices and MRR

Syncro keeps a contract and its billing in two places: the contract record, and the recurring invoice schedules that actually bill. The money spine is the schedule lines, so that is what Current reads for MRR. A schedule that belongs to no contract still counts: Current gives it a header of its own so its revenue is not lost.

Syncro	Current	Direction
Contract name, dates, amount	Contract header	In
Recurring schedule frequency	The billing period on each line	In
Schedule line item: product, quantity, price	Contract service line, priced per line	In
Schedule line cost	Vendor cost, when Syncro publishes one	In
Paused schedule	Line marked inactive	In
Invoice line items	Billed items behind account profitability	In

Note

Each line is normalised on its own cadence

Syncro bills on nine cadences, from daily to every three years. Current converts each line to a monthly figure using that line's own frequency, not the contract's, so an annual line is divided by twelve and a triennial line by thirty-six. A frequency Current cannot read is stored as unknown on that line, and the line then falls back to the contract's own billing period; a line with no readable cadence either way is counted as monthly until the frequency is mapped. The sync names the frequency it could not read, and that is worth acting on the same day: an unmapped yearly line reads as its full amount every month, on the company record, on the whitespace grid and in account profitability.

Estimates

Syncro	Current	Direction
Estimate, any status	Quote on the company record	In
Approved estimate	Won quote in the win-quote queue	In
Declined estimate	Quote marked lost, and the linked deal closed lost	In
Line items: product, quantity, price	Quote lines, classified by product category	In
Estimate status	Approved, written only by a person converting a quote in Current	Out

A Syncro estimate line carries a product, not a recurring or labour flag, so Current asks you once which product categories are recurring, which are one-time and which are labour. That mapping lives on the Syncro card and every future estimate classifies itself from it.

Appointments and time off

Syncro has no PTO record and no holiday calendar, so availability comes from appointments. Every appointment becomes a busy block for the people on it. An appointment whose type name reads like time off, PTO, vacation, out of office, holiday or leave, becomes time off, which the scheduler treats as a hard absence and works around. Anything else stays busy, which is shown on the calendar but never moves a date.

Holidays on a Syncro workspace are kept in Current, the same as on ConnectWise and HaloPSA. Add them under Settings, Holidays and the scheduler skips them.

What is deliberately not synced

Not synced	Why
Company notes	Syncro has no note log, only one free-text field on the customer. Appending Current's notes into it would rewrite a field your team owns, so notes stay in Current. Ticket comments are different and do sync.
Company attachments	Syncro has no company attachment surface.
Contact notes	Current reads a contact's name, email, phone, mobile and title. The notes field on a Syncro contact is not read and never written, so a note typed on either side stays where it was typed.
Phases and dependencies	Syncro has neither. Both stay in Current, where the scheduler uses them.
Estimated hours and percent complete	A Syncro ticket carries neither. Current keeps its own.
CSAT	Syncro has no survey API. On a Syncro workspace, CSAT comes from CrewHu.
Cost rates	Syncro does not publish an internal cost rate through its API, so set them in Current under Settings, Cost rates. A rate you enter is never overwritten by a sync.
Scripts and remote actions	Current never runs anything on a customer's machine. Asset and alert data is read-only.

Was this helpful?

← Previous

Prepare your Syncro before onboarding: the setup checklist

Syncro estimates and quote-agnostic conversion