Migrate Design Studio assets

[Anonymous]

Hi guys,

Any of you have had a migration of instance and if so, how do you dealt with the "moving" of the Design Studio assets please?

Kind regards,

Raúl

[Grégoire_Miche2]

Hi Raul,

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

-Greg

[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.

[Anonymous]

Hi guys, awesome thank you!

[Jep_Castelein2 · Accepted solution]

clone them into a Program, then import the Program into the new instance. For Forms, make sure the fields also exist in the destination instance. Same for Lead tokens in Emails/LPs. Dynamic Content & snippets not supported in Program Import.

[Anonymous]

Hi Jep,

Do I have to move them back to Design Studio after I import the program with the assets in the new instance?

I wanted to compare the 2 instances to see what are the differences between assets (due I don't know which ones are missing in the new one). I have 500+ emails and 900+ images/files. Do you know a way to get that easily? Only Landing Pages are "exportable" to excel...

Thank you!

[Grégoire_Miche2]

Hi Raul,

Yes, you probably will want to move them where they were located originally.

We always recommend the following practices to our customers:

• Only locate templates and forms in the design studio. Shared forms make for a much simpler maintenance, as forms sometimes have to be modified.
• All emails and landing pages should be located within programs in the Marketing activities.

Excepted with some API dev to get a complete listing of all the assets, there is not simple way to compare the assets in 2 instances.

-Greg

[Anonymous]

Hi Greg,

Thanks for your reply. So even if I don't move them back to their "original" location, will the links work? Like Landing Pages or Emails referencing images?

Best regards,

Raul

[Grégoire_Miche2]

Yes, all the more so as Images are referenced by their URL.

BUT, 2 issues may arise :

• If the LP's in the new instance are published in a domain that is different from the domain used in the previous domain, you have cross domain content situation that might become tricky (unsecure content) if the new instance moves to HTTPS
• in the LP editor, I have observed that images from other Marketo instances sometimes do not display.

-Greg

[Anonymous]

Hi Greg,

I just checked and mi new instance (migrated by old one) does reference the old instance images, so when Marketo removes the old instance, all my 500+ programs will be useless?

[Grégoire_Miche2]

HI Raul,

Yes, I am afraid. there is no easy way out of this, excepted with the Assets REST API or may Marketo PS.

-Greg

[Anonymous]

Hi Greg,

I have imported a program from our old instance to our new one. It created a duplicate of the templates that it uses (a shame but have to live with it for now). It didn't bring the images that the emails and landings use.

I am so afraid that when we update the CNAMEs, all the sent emails will be linked to the new instance and they wont find the images and we will have nothing but a lame email with error messages saying that the image was not found. Do you know if this will happen or what can I do to avoid this?

Thank you!

[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

[Dan_Stevens_]

Raul - we've had similar experiences when using the "import program" functionality.  Lots of duplicates; and assets/images missing.  We therefore don't use this capability.

[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.