Syncro sync: the complete field-mapping reference

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.

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.

Syncro has no parent company or Top Level field, so customer groups stay in Current. Grouping, changing or deleting a group writes nothing to Syncro, and the group's site list says so. See "Customer groups: one customer with several sites".

Contact addresses follow the same rules as on Autotask. A Syncro contact with no address never clears one Current already holds. Saving a contact in Current sends it to Syncro right away, its address included, and until it reaches Syncro the next sync keeps your changes rather than putting Syncro's old values back. An address field you clear in Current is not cleared in Syncro. A new contact created from Current with no address of its own is created in Syncro with its customer's address. To fill the address of existing Syncro contacts, a tenant admin opens Integrations, Syncro, Sync behavior, and uses "Contacts · fill blank addresses from the company". Preview lists every contact with no address at all that would get its customer's Syncro address, and every contact skipped because its customer has no street or city. Fill stays off until Current has seen one Syncro contact that carries its address fields. Filling asks you to type FILL, reads each contact from Syncro again just before changing it, follows your CRM write mode (in Test mode, only ZZ-Current Test customers), and records every change in the audit log.

Syncro Leads serve two purposes: sales opportunities and the inbound email queue. Only the sales ones become opportunities. 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. A sales Lead with no customer behind it gets a prospect company in Current so the opportunity has somewhere to live, and that company is never created in Syncro. Syncro does not return the opportunity amount on its Leads list, so an opportunity from a Lead arrives with no value until somebody fills one in.

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.

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.

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.

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.

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.

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.