Migrate Design Studio assets

[Anonymous]

Hi Dan,

So you manually updated the programs or what was your workaround?

- Raul

[Dan_Stevens_]

If needed, yes.  Often when we run into an issue with cloning between workspaces (when there's a bug somewhere), Support will recommend the "program import" functionality.  And then I let them know that this causes more headaches for us that just re-creating the program from scratch.

[Grégoire_Miche2]

Hi Raul,

Duplicating the templates has been a known issue for a long time. See

With regards to the emails links, the easiest way to solve the issue is to create another CNAME from the old domain to the new instance and domain redirect in your new instance as soon as you have completed importing the images and files in the new instance and you stop using the old instance.

But, as Dan, I avoid using the import program functionality as much as I can.

-Greg

[Grégoire_Miche2]

Furthermore, recreating programs in the new instance is often the opportunity to streamline them and start with a new, clonable, program template, new HTML templates as well.

-Greg

[Grégoire_Miche2]

Hi Raul,

I understand that Marketo PS also has an instance migration service.

-Greg

[Anonymous]

Hi guys, awesome thank you!

[Jep_Castelein2]

yup, we have migration scripts that use the API to copy over all images, update references, etc. But scripts or no scripts, a migration is always a lot of work unfortunately. This type of manual migration is necessary when you are merging instances. If you want to migrate everything to a new instance, we can use 'instance copy' which copies over all assets. Leads or activities won't come over in an instance copy.

And just FYI, if you are getting a new Marketo instance because of a change in CRM system, there is now an experimental "remove CRM" option that enables reconnecting an existing Marketo instance to a new CRM system.

[Anonymous]

Hi Jep,

Thanks for your response.

I already did the migration because our CRM also did it. The remove CRM would be awesome. We had issues in the migration and it took 15 days more than expected, due this, we had to keep using the "old" instance wile the new onw was being fixed, that is why I have this problem with new programs and update programs and of course all the used assets.