Upsert your missing data without affecting the historic logs

Upsert your missing data without affecting the historic logs

Dear Customers,

We hope you're well!

Migrating your data from a legacy system to Zoho CRM is a critical operation as it deals with treasured data. In an unfortunate event, if you have missed to move your historical datasets, you have had to repeat the migration process all together to protect the integrity of their timeline. With a huge volume of data at hand, repeating this process is painstakingly redundant and time-consuming and that's why we have come up with a useful enhancement to upsert data.

The Upsert operation 

Upsert is a database operation that enables you to update data to an existing record or insert data to the original database while simultaneously ensuring relevance and accuracy.
 
As opposed to module imports where data added or updated is considered as edits to the records, upserting datasets is meant to patch the data with the existing database without altering their chronology and timeline.

How are we ensuring integrity while restoring missing data?

While our goal is to restore missing data to the database seamlessly, we are also aware of how the migrated data could have been put to use in Zoho CRM or how the older values could have been altered, changing their original timestamps. With these potential consequences in place, upserting missed data might question its relevance to the current process and thus we are leaving the decision to choose the desired data at the hands of admins through an action called Upsert Resolution.
 

The Upsert resolution:

Upsert resolution is like a gatekeeper. Based on the nature of your conflict, it lets you decide what desired data to upsert.

At this juncture, you have two data at hand:
  • Data already migrated to the system
  • File with data to upsert
 
As an admin, you would have a better knowledge of which data is right at the time of upsert. You would know if it is better to keep the new values per the process or retain the legacy values. Based on this judgment, you can choose your upsert resolution.

Untouched records indicate migrated records that are not modified after migration. By selecting untouched records as upsert resolution, you are intending to update only those records that are not "touched" for modification.

Selecting "All records" instructs the system to update all records in the system irrespective of them being modified after migration or not.

If you'd like to restore or retain empty values, you can also do so after selecting this preference.

That's all about seamlessly stitching legacy data back to its database. If you have questions or feedback about this enhancement, drop them in the comments section—let's connect!

Info
Release plan: The Upsert operation is available for customers in all DCs.
Editions: Available for editions from Free to Ultimate
CRM Availability: You can use this Upsert operation in both the UIs.

 
May the right data win!
 
Kind regards,
Saranya Balasubramanian,
CRM Marketing