Reltio Connect

Hi ReltioTeam,

I am writing to inquire about the most efficient method to handle a data migration task for our production environment.

Context:
We are enhancing our integration with the Swift Source for both Individual and Organization entities. Our new logic will check for an existing "Physical Location" address from Swift. If present, it will automatically create a copy in a new address attribute named "Swift Physical Location."

The Challenge:
This new logic will only apply to records processed after the deployment. We have a backlog of historic Individual records that already have a "Physical Location" populated from Swift. For these records, we need to manually create the corresponding "Swift Physical Location" address attribute during our production migration.

Request:
Is there a built-in method or recommended best practice within the Reltio platform to perform this kind of bulk copy operation efficiently? For example:

A bulk PATCH operation via the API?

A configuration-based data transformation job?

A specific "copy" function within the Console or a utility you can provide?

We want to avoid manually updating each record and are seeking a scalable solution. Any guidance, documentation, or method you can provide to assist with this task would be greatly appreciated.

Thank you for your time and assistance.

Hi,

I think I understand the problem.  Can you give us some idea of the scale?  You mention this is for people and organizations.  Are these locations reference attributes?  if so, can the location be updated directly?  How many locations need to be updated?  10's of thousands?  10's of millions?

Thanks for the response!

We have around ~275k records These arent reference attributes, instead you can think of them as a secondary address.  

Let me know if you have anymore questions

For 275k, I don't think efficiency is your biggest worry.  Personally, I'm a card carrying member of the 'brute force' school.  I would export the entity type to get the id's and address values involved in a file.  Then I would use RIH or the integration tool of your choice to call the entities API with partial update to populate the new attribute.  Don't forget to give your update a crosswalk!