Marketo Instance Refresh | Community
Skip to main content
Dave-Silva-2
Level 3
June 17, 2024
Solved

Marketo Instance Refresh

  • June 17, 2024
  • 1 reply
  • 3040 views

Hi all,

 

We are considering doing a full instance refresh -- has anyone completed one recently that could outline their experience?

For example, is everything refreshed/changed, including your munchkin ID?

 

I couldn't find good information on the process and implications.

 

Thank you!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Dave-Silva-2

Interesting recommendation. Who is supposed to conduct this refresh? You or Adobe Professional Services?

 

It's certainly good practice to keep your Marketo instance tidy. Archive programs, hide/delete unused fields, turn off unnecessary processes and delete unengaged people from your database. But I would consider this to be an ongoing process, and I've never heard Adobe recommend a "refresh" or a "deep clean". But I'd love to hear what it's supposed to entail.


This is the response I received so far. I was hoping it would have more technical details, which I'll update here if/when I receive them.

 

 

Manual Cleanup in Current Instance

  • Effort: High, as each field needs to be reviewed and deleted individually.
  • Tools: Marketo provides tools and APIs to manage fields, but bulk deletion still requires scripting or manual intervention.
  • Risk: Moderate, as there is a risk of impacting live processes and data.

 

Replacement Instance Setup

  • Effort: High, but more structured. Requires planning for data migration, integration setup, and user training.
  • Tools: Marketo's migration tools and APIs can facilitate data transfer, but custom scripts or third-party tools might be needed for complex migrations.
  • Risk: Moderate to High, depending on the complexity of the current setup and the thoroughness of the migration plan.

 

 

Recommendation:

 

If the Current Instance is Highly Customized and Critical:

  • Recommend manual cleanup to avoid the risks associated with migration.
  • Use Marketo's API to script the deletion of fields to reduce manual effort.
  • Implement a phased approach to minimize disruption.

 

If the Current Instance is Relatively Simple or Rockwell Can Handle Migration Themselves:

  • Consider spinning up a replacement instance to start fresh.
  • Plan the migration carefully, ensuring all critical data and configurations are transferred.
  • Use this opportunity to optimize and streamline processes.

1 reply

Michael_Florin-2
Level 10
June 18, 2024

What do you mean by "Instance Refresh"? I suppose you mean setting up a new Marketo instance and beginning from scratch?

 

That is usually done when you're forced to do it by outside circumstances such as switching integrated CRMs or merging two Marketos after an acquisition. Yes, in that case the Munchkin ID changes and you have to redo your website integrations. But apart from that it's "just" setting up a new instance. Depending on what exactly you want to migrate from old to new and how much you have learned since setting up the old one, it's both a long and painful process as it is liberating and fun.

Dave-Silva-2
Level 3
June 18, 2024

Thanks Michael.

 

We were chatting with our Account Director about doing a deep clean of our instance and he recommended a "refresh".

He said that customers typically did it every several years.

 

If setting up a brand new separate instance is the only option, then it's certainly more of an undertaking.

We're awaiting more information, but I was hoping it was really more of a "refresh" than a "start from scratch".

Michael_Florin-2
Level 10
June 18, 2024

Interesting recommendation. Who is supposed to conduct this refresh? You or Adobe Professional Services?

 

It's certainly good practice to keep your Marketo instance tidy. Archive programs, hide/delete unused fields, turn off unnecessary processes and delete unengaged people from your database. But I would consider this to be an ongoing process, and I've never heard Adobe recommend a "refresh" or a "deep clean". But I'd love to hear what it's supposed to entail.