How can I sync the Contact Owner/Source fields?
Yes, you can!
However, as you've probably noticed this field may not be available in the Field Mapping like any other field. Instead you will have to map this field in the connection Rules. See below on how to do so with contact owners:
On this image you can already see one reason why PieSync does not display these fields in the field mapping. The way ownership works can differ vastly per app — not to mention that not every app may have the same owners. In this case Copper distinguishes on name, while HubSpot on email address.
As such, we've found that the best way to enable you to sync your owners, is through the filters and action. The downside here is that you will have to create a separate rule for each owner that you want to keep in sync.
The rule itself also does not guarantee that PieSync can sync it 2-way. Only when the "other way around toggle" appears below the rule will that be the case.
When looking at the way the Source fields work, we find a similar situation. If you are not able to map the source field through the Field Mappings, you can try to do so through the Rules:
The Source field often does exist in the Field Mapping, but connecting it to another source field probably doesn't work. That's because both or one of these fields is a dropdown field. PieSync is not able to see which values should be mapped to one another and will require you to do so on its behalf.
What if this solution does not work for you?
In that case, you are either bumping against a limitation of the API of one of your apps or against a limitation of PieSync. Feel free to reach out to firstname.lastname@example.org to have us investigate it and see if there's something another workaround.