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.