Marketo Instance Migration - What to Know

Question

Hello everyone, 
 
We are in the process of working to re-deploying a new Microsoft Dynamics CRM environment later this year, and as a result we are also preparing to set up and transition to a new Marketo instance. 
 
We have been in contact with our CSM with Marketo and they are aware of our project and will assist with standing up the instance, but I'm trying to gather some information on what our team can expect when we get to the point of starting to move our assets, programs, and lead database to our new instance. 
 
Does anyone have any insights into how the process worked for them? When it comes to actually moving assets to the new instance, what does that process look like? How long did you prepare for the transition and how long did the transition take for your team? We're trying to gather insights into what the actual work consists of. 
 
 Please let me know of any clarifying questions and I appreciate the insights!
 
Thank you, 
Alec

mchakraborty · Answer

Hi Alec,

I am currently working with Adobe on a similar instance migration as a part of MSD CRM cloud migration.

The process for us was quite intensive due to sheer database, activities, and program database size. However, Adobe professional services team were great to work with and planning the migration.

The program and asset migration are done by scripted migration and Adobe will essentially clone your current instance and build it in a new instance. Having said that, it is an elaborate process as all the configurations, integrations and administrations will be changed and will need to be implemented and tested. Thus, you will need your Marketo Administrators, CRM Administrators to work with Adobe throughout the migration process.

Potential issue:

Depending on the volume of stand and custom object records synced from MSD to Marketo, there can be a long initial sync cycle for migration.
Activity, program membership & Static list membership data migration consumes a lot of rest APIs and can cause downtime for other rest API integrations.
Delta program and asset migration can be only done manually. Once the instance is copied and migrated, the programs and updates made to your old marketo instance in the delta period will need to be migrated manually.

When you are planning for a migration, I would suggest keeping a few key things in mind to ensure your process is smooth.

Database clean-up – Audit your Marketo database and delete any inactive/redundant records, custom entities to keep the database volume to minimum.
Create a Data Dictionary – Data dictionary of all Marketo ONLY, CRM standard object fields and custom entity fields will be very helpful.
Rest API limitation – Depending on the size of your Marketo instance upgrade your Rest API limitations
Delta Migration Log – Keep track of any changes or updates made to your Marketo instance during instance copy/migration period to migrate delta changes to your new instance

Thanks

Malay

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded