Allow Assets to be Transferred Between Marketo Instances

[Anonymous]

I know we can transfer Programs between instances by requesting the Marketo Support team to do so. We'd like to have the ability to transfer Smart Lists (for example) from Lead Database to another Marketo instance. 

This would be a big timesaver for ourselves as we manage several instances on behalf of clients, and have multiple standardised smart lists for the purpose of email reputation management. 

[Anonymous]

This can be done now out-of-box via the download program feature. Support just needs to link the instances

[Anonymous]

Hi Mark: We do use the feature you mention quite often, but I'm requesting a similar feature for lists (or even whole folders of lists) in Lead Database.

The current steps for achieving cloned Smart Lists from one instance's Lead DB to another are as follows:

1. Clone each Smart List one-by-one to a Program in Marketing Activities
2. Request the instance link from Marketo support
3. Import the Program containing Smart Lists to the new instance
4. Clone each Smart List one-by-one to Lead DB

Adding the ability to transfer assets directly between Lead DB's would save time and reduce the chance of user error - which will always be useful for Marketo users who manage multiple instances!

[Anonymous]

Seems like the smartlists would come over if they were local assets. I have not tried this yet. Let me know if they do...

[Anonymous]

Mark is correct that you can copy smartlists from one subscription to another, if it is a local asset within a program. You can not currently copy a smart list from the Lead Database tab to another subscription.

[Anonymous]

Right. You will need to "move" your smart list to a program to make this work.

[Anonymous]

Hi Adam-
I ran into this issue as well - and I would support this as cloning between instances seems to be primarily focused on LPs and emails (and programs) and not the smart lists or static lists.  One of the mroe frustrating things with a clone between systems is when a localized asset (like email or LP) references something that is not in the new instance and you get a partial failure. If you import between instances, the program clone will be a success but the individual elements (if they fail) are not readily apparent.

The specific issue I had was that my emails used a snippet (for salutation) and the clone happened but the individual elements that referenced the snippet (like the email) failed upon import.

Plus, with little to no documentation around the clone procedure, it seems to be a "try and learn procedure".