2026-05-10-auto-mapped-field-mappings
Field mappings now propose themselves
When you set up a new sync, Oneprofile matches your source fields to destination fields automatically. The matcher works through five tiers: mappings you've used before for the same pair of integrations, exact name matches, common synonyms, fuzzy substring matches, and finally a "create new property" fallback for fields that don't have a home yet. A summary banner at the top of the mapping step tells you how many fields matched, how many will create new properties, and how many still need a manual decision.
Five-tier matching with past, exact, synonym, substring, and create-new tiers
Banner shows matched, new-property, and unmatched counts at a glance
Past mappings remembered per source-destination pair, so the second sync of the same shape sets up faster than the first
Type-aware matches so a date field never lands in a string column
Smarter record type defaults during sync setup
The sync wizard picks sensible record types up front instead of leaving the dropdowns empty. Person-shaped record types (contact, customer, user, profile, member) are prioritized when there's more than one option, and the destination follows the source: pick "contact" on the source and the wizard picks "customer" on the destination. If you override the suggestion, your choice sticks.
Source defaults to a person record type, then a company record type, then the first available
Destination auto-selects the closest matching record type as soon as you pick the source
Manual selection is preserved across edits
Partial failures get their own status
Sync runs that finish but couldn't write every record now show a "Completed with errors" status instead of being lumped in with successes or failures. The chip on the runs dashboard turns yellow so partial failures stand out from the green completed runs.
New run state appears anywhere a sync run status is shown
Warning color so you can spot partial failures from a list
Per-record errors and counts work the same way as before
Brevo: contact properties, list filtering, and company records
Brevo is now a much bigger destination. You can sync custom contact properties (create, list, and delete them from Oneprofile), filter Brevo contact reads on last-updated and arbitrary fields, and sync Brevo companies as a first-class record type for B2B use.
Custom property creation, listing, and deletion for Brevo contacts
Last-updated and field-level filtering when reading Brevo lists
Company record type with create, update, and list support
Empty state on the syncs page
Connected an integration but haven't built a sync yet? The syncs page now shows your connected integrations and a clear path to create your first sync, instead of an empty list with no next step.