Use Cases for a Marketo Backup Solution

[Rachit_Puri2]

Hi Community Members

We just launched a new product for Marketo, M-Hive which can take a regular back-up of your emails, landing pages, and templates. We created this app to help marketing teams where different team members are working on assets, and want to keep a back-up if assets are modified or deleted incorrectly. More details here: http://go.grazitti.com/M-Hive-Marketo-Asset-Backup.html

Additionally, it allows you to preview multiple assets simultaneously and even export a PDF. If you have an email with HTML and text version in 56 different language segments, the app can simply generate a PDF with a preview of email in 56 versions each for HTML and text.

We would love to hear what more can be included in the app as features, and if there are any use cases we should consider for the product roadmap.

Regards

Rachit

[Grégoire_Miche2]

Hi Rachit,

Could it backup some assets form one instance and insert them in another one?

see Assets replication across different marketo instances

Other use cases are:

• The sandbox - production organization
• consultants (like us) creating assets in one dev instance and needing to publish them in another one

-Greg

[Rachit_Puri2]

Hi Greg

Yes, we are implementing a functionality where we can take a back-up from one instance and deploy the assets in another instance. It will be very helpful for agencies.

For Sandbox to Production, doesn't that already happen by importing programs from Sandbox to Prod? Our solution could do that but not sure if that would be a pressing need. Would still include that as an option in the app.

[Grégoire_Miche2]

Hi Rachit,

Cross-instance asset sharing should be done comprehensively, together with dependant objects.

Specifically, if move a LP or email template, I also want to have all images in this templates, all defaults snippets in snippet elements, moved as well and their references changed in the target instance.

-Greg