This post is the second one of a 3 parts series, stating with this one: Testing the email editor 2.0: Great features, a few glitches and the strong need for a v2.1, which dear reader, you should read first in order to understand the reasons of this migration path.
You should also read this Email editor 2.0 is leaving room for a v2.1 in order to get a grasp on the remaining limits of the products and avoid to look features that are not there yet.
From all the testings in the post above, we have designed a migration path that we will apply to our customers in order to make sure that everything runs smoothly and no key content get lost.
Table of content
The very first thing you need to do is to define your strategy. You current templates will have to be divided in 2 categories:
At the end of the upgrade process, you will end up with 3 types of templates:
Before you activate the new editor, we strongly advise that you take these preliminary steps:
Just after the activation of the feature, and before you authorize anyone to start using the editor, you should run this series of sanity checks:
At this point, you are done with the upgrade and you can benefit from the new UI.
In large orgs, you may want to deactivate the starter template library, in order to avoid your users starting to create emails that are far from your corporate guidelines.
Your upgrade went well, here are some quick wins should you look for in order to get rapidly some more value from the editor, through new or cloned templates. We recommend that you do not try to introduce v2 features in upgraded templates that have production emails attached to them and rather create new ones.
On the longer term, invest in the new possibilities offered by the new features
Continue the reading here: Email editor 2.0 is leaving room for a v2.1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.