Marketo-to-Marketo Migrations - Scripting

AmritTandon
Marketo Employee
Marketo Employee

Now that you know what is Marketo-to-Marketo Migration, this blog will help you understand how to use scripting to bring data to the new instance.

 

Do you want to migrate cookie data, membership data, activity history data, and files and image from source to new instance?

 

If the answer is yes, it is possible via Marketo APIs. Marketo Technical Consulting team has built scripts using Marketo’s APIs that will copy over cookie, membership, and activity data (for people matched in both instances). Images and Files can also be migrated via APIs.

 

What are the requirements for utilizing scripting?

 

People data should be present in the new instance. Before bringing this data, discuss with Marketo Engage Technical Consultant, to determine a field (dedupe field) that can uniquely identify the record in both the instances and how to leverage that in this migration process. Eg. If a person A is present in source instance, then the scripts need to identify and establish a 1:1 relation between this record and the record in the destination instance. So, choose this field wisely.

 

Different examples of ‘dedupe field’ are:

  • Marketo Id

Example:

  • Sync Marketo Id of records in source system to the CRM connected with source system
  • Migrate CRM and copy over this new field holding Marketo Id
  • Sync this field as a custom field when connecting new CRM with new/destination Marketo instance
  • Any other unique identifier field in your source system like customer id, client id
  • Email Address
    • Only when there are no duplicates by Email Address in source instance

 

How will the script behave if there are duplicates?

 

Let’s assume ‘email’ is selected as the dedupe field for bringing over data points. There can be three scenarios:

 

Email Address is present multiple times in Source instance but once in Destination instance

  • Mapping will be created
  • All the data (that can be migrated) from duplicate records in the Source instance will be migrated to the one matching record in Destination instance

Email Address is present multiple times in Destination instance but once in Source instance

  • Mapping Error as there will be “Multiple records with the same email” in destination instance
  • No unique mapping, so data won’t be migrated

Same email address is present multiple times in both source and destination instance

  • Mapping Error as there will be “Multiple records with the same email” in destination instance
  • No unique mapping, so data won’t be migrated

 

 For more information the scripted data migration, discuss with your Customer Success Manager or Technical Consultant(s).

81
0