Record matching
Match records that already exist prior to turning on sync.
Last updated
Match records that already exist prior to turning on sync.
Last updated
Before turning on sync, you may already have data in both of your apps. For example, if syncing Salesforce and Postgres, you may might have contact records in each:
With record matching, you can tell Whalesync how to match and merge these records when you turn on sync for the first time.
In this example, we might match on the email field since that field is unique for each record.
Note - record matching only runs during the initial sync to match records that existed prior to activating your sync.
Sometimes matched records do not have the exact same data in every field. In these cases, you can choose which app's data should take precedence.
We strongly suggest matching with unique fields (like IDs) wherever possible. If you match on a non-unique, Whalesync will alert you to any records that cannot be matched because they are not unique.
In these cases you can optionally add a second matching column. This tells Whalesync to first try to match records on the first column, then try to match records on the second column.
Alternatively, you can move past this screen even if you have non-unique values but be aware that those records will not be able to be matched which can result in unwanted duplicates.
