The migration of objects between Salesforce Marketing Cloud accounts or business units has, until now, been easy to describe: Copy, paste, copy, paste, copy, paste, etc. You’re transferring data from a browser that is logged into one account into another logged into a second. And when you think you’ve reached the end, you’re likely to find that the email you just recreated had referenced portfolio items and content areas that you now have to track down and copy over as well – leading to hours of research and discovery into what other items need to be moved, resulting in still more copy, paste, copy, paste, copy, paste.

Simply put, it has been a labor-intensive project. DEG is Salesforce Marketing Cloud’s largest and most-decorated partner, and we have seen that situations more times than we can recall. So it was time to find a better way forward.

 

ExactTarget Migration EngineMeet Reactor

Starting with a set of productivity tools we developed for our internal Salesforce Marketing Cloud team, we built Reactor – a powerful engine that offers an efficient and accurate migration between Salesforce Marketing Cloud accounts.

Where migrating items between Salesforce Marketing Cloud accounts or business units is a risky proposition rife with potential for human error and missed requirements. Reactor mitigates those issues by creating a repeatable automated process for migrating items. Not only will it migrate the email, but it will also dissect the HTML, pulling out all of the AmpScript and embedded HTML references to other Salesforce Marketing Cloud items, migrating those as well. And it will do this recursively, meaning if a content area is found in an email, that content area and all of its content areas (and all of their content areas, etc.) will also be scanned for dependencies. It also works similarly with items such as queries and data extensions. Further, if one of the dependencies found is renamed or has its reference changed (i.e. a portfolio item’s URL), Reactor will find and update all the references so they aren’t broken in the new account or business unit.

 

Preserve folder structure

Another powerful feature is Reactor’s awareness of the folder structures in an account. Let’s say you have a fairly in-depth folder structure where your portfolio items are meticulously organized – something like: “Portfolio201351LifestyleOutdoorsMenCasual.” When migrating portfolio items from those folders to another account or business unit, Reactor automatically maintains your folder structure in the destination account or business unit.

You’ll also get a lot of mileage out of Reactor’s ability to translate profile attributes to data extensions. We’ve seen quite a few companies moving away from lists in favor of data extensions, mainly for flexibility and performance reasons. What better time to do this than when transitioning to a 2.0 account? Reactor allows you to take a set of profile attributes and convert them to data extensions. What’s left is the subscriber export and data import. It’s that simple.

 

Migrating many to many

Reactor is not just a 1.0 to 2.0 Salesforce Marketing Cloud account migration tool, or even a business unit-to-business unit migration tool – though it is all of these things. It’s also a many-to-many migration tool, capable of consolidating any number of Advanced 1.0 accounts into a single Enterprise 2.0 account with 200 different business units. Or, conversely, it can consolidate a number of Enterprise 2.0 accounts into a single Advanced account. In certain scenarios, it could even be used for simply copying Emails or Content Areas to different names inside the same account.

Migrations can be daunting tasks, even understanding the significant benefits of undertaking them. In fact, we often see organizations that are in the uncomfortable position of having to continue taking the extra time and trouble rather than go through what has previously been an expensive and costly process – especially when they feel like the end product won’t be accurate.

If you’re in that position, then let’s connect and talk about what Reactor can do. But in the meantime, here’s a quick rundown of Reactor’s capabilities:

 

Automatic Folder Creation

  • Given a path to a folder (ie: My EmailsMigrated20135Birthdays), the same structure will be built in the destination account.

Dependency Detection

  • Given an object Reactor will traverse through that objects content and look for references to other objects.
  • Portfolio Detection

–       Image AmpScript function

–       GetPortfolioItem

–       Html url references

  • Content Area Detection

–       ContentArea AmpScript function

–       ContentAreaByName AmpScript function

  • DataExtension Detection

–       Use in Queries (both the query and the Target)

–       ClaimRow AmpScript function

–       ClaimRowValue AmpScript function

–       DeleteDE AmpScript function

–       InsertDE AmpScript function

–       Lookup AmpScript function

–       LookupOrderedRows AmpScript function

–       LookupOrderedRowsCS AmpScript function

–       LookupRows AmpScript function

–       UpdateData AmpScript function

–       UpdateDE AmpScript function

–       UpsertData AmpScript function

–       UpsertDE AmpScript function

  • Email Detection

–       Use of Email in a List Automated Email

 

Dependency Replacement

  • Assuming an object’s name, external key or any other identifier used in dependency references is changed in the migration progress. References to that object will also be replaced in all objects found to hold them as a dependency.

–       Perfect example of this is Portfolio URLs.

 

Dependency Resolution

  • Given an object is selected for migration, Reactor will first detect all dependencies and include ones that weren’t found in the migration.

 

Example of Detection/Resolution/Replacement:

  • Only a single email is chosen to be migrated. Reactor will find all ContentAreas and Portfolios and DataExtensions references in not only the HTMLBody, but in ContentAreas references in the HTMLBody and add them automatically to the migration with no manual effort in detecting them.

 

Supported Objects

Email

  • Select to migrate by:

–       ID

–       Name

–       Folder

–       External Key

–       Object ID

  • Dependency Detection/Resolution/Replacement of:

–       Content Areas

–       Portfolio

–       DataExtension

  • Renaming
  • Re-External Keying
  • Assigning a destination folder by:

–       New folder by ID

–       Automatic Folder Creation to a specified location (by default is the Current location in the source account)

 

  • Content Area
  • Select to migrate by:

–       ID

–       Name

–       Folder

–       External Key

–       Object ID

  • Dependency Detection/Resolution/Replacement of:

–       Content Areas

–       Portfolio

–       DataExtension

  • Renaming
  • Re-External Keying
  • Assigning a destination folder by:

–       New folder by ID

–       Automatic Folder Creation to a specified location (by default is the Current location in the source account)

 

  • Portfolio
  • Select to migrate by:

–       ID

–       Name

–       Folder

–       External Key

–       Object ID

  • Renaming
  • Re-External Keying
  • Assigning a destination folder by:

–       New folder by ID

–       Automatic Folder Creation to a specified location (by default is the Current location in the source account)

 

Data Extension

  • Select to migrate by:

–       ID

–       Name

–       Folder

–       External Key

–       Object ID

  • Renaming
  • Re-External Keying
  • Assigning a destination folder by:

–       New folder by ID

–       Automatic Folder Creation to a specified location (by default is the Current location in the source account)

 

Profile Attributes

  • Select to migrate by:

–       Name

 

Queries

  • Select to migrate by:

–       ID

–       Name

–       Folder

–       External Key

–       Object ID

  • Dependency Detection/Resolution/Replacement of:

–       Data Extension (will also detect moves to/from Shared folders)

  • Renaming
  • Re-External Keying
  • Assigning a destination folder by:

–       New folder by ID

–       Automatic Folder Creation to a specified location (by default is the Current location in the source account)

 

List to Data Extension Conversion

  • Able to select all or a subset of profile attributes on the account and convert them to 1 (or more) Data Extensions.
  • Able to perform transformations on the attributes (name, data type, display order).

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Comments