{"id":24749,"date":"2021-03-09T10:37:18","date_gmt":"2021-03-09T15:37:18","guid":{"rendered":"https:\/\/www.litmus.com\/?p=24749"},"modified":"2024-04-17T14:15:16","modified_gmt":"2024-04-17T18:15:16","slug":"how-to-do-an-email-audit","status":"publish","type":"post","link":"https:\/\/www.litmus.com\/blog\/how-to-do-an-email-audit","title":{"rendered":"How to do an email audit"},"content":{"rendered":"\n\n\t
\n
\n \t
\n \t\t
\n \t\t\t
\n \t\t\t\t

You may have seen our recent posts in our ESP Migration blog series: New CMO. New MarTech stack. What now?<\/a> and Considering a new ESP? Top 7 questions you need to ask first<\/a>. This is the next one in the series. Once you’ve decided to make the move, the next step we recommend is to do an email audit. Doing an audit of your program before you take the steps to actually migrate ESPs will help you:<\/p>\n

    \n
  1. Gain a clear picture of exactly what you need to migrate to your new ESP.<\/li>\n
  2. Understand what emails and programs you don\u2019t need anymore.<\/li>\n
  3. Identify any gaps in your email program for you to tackle post-migration.<\/li>\n<\/ol>\n

    So, just how do you do an email audit? Let\u2019s take a look at some easy-to-follow steps.<\/p>\n

    \n\n\n\n
    \"The<\/td>\n\n

    Everything you need to know to migrate ESPs<\/strong><\/p>\n

    An email audit is just the beginning. Planning an ESP migration? We\u2019ve got your back with a complete guide\u2014including planning templates\u2014so you can get it done right.<\/p>\n

    Get your guide \u2192<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    <\/h2>\n

    Step 1: Documentation<\/h2>\n

    No matter how small or large your email program is, it probably consists of multiple assets, emails, and things spread across countless different apps, programs, and file systems. Bring them all together in one document to give you a view of exactly what you need to bring with you to your new ESP.<\/p>\n

    Step 2: What do you need to document?<\/h2>\n

    Great question. Think about all the pieces that make up your email program. Even the less tangible pieces of your email program. For example, rules you commonly use for lists or segmentation. You\u2019ll need to recreate these in your new ESP. You\u2019ll likely have:<\/p>\n

      \n
    1. Emails (in and outside your current ESP)<\/li>\n
    2. Email templates (in and outside your current ESP, unless you have Litmus)<\/li>\n
    3. Media assets, including images<\/li>\n
    4. Automations or email flows<\/li>\n
    5. Landing pages<\/li>\n
    6. Forms<\/li>\n
    7. Lists<\/li>\n
    8. Segments or rules<\/li>\n
    9. APIs<\/li>\n<\/ol>\n

      This step will take some time and should be a collaborative effort. You may not be the only person at your organization using your ESP, so put the call out to other members of your team. Ask them the important question of what they may need to migrate to a new ESP.<\/p>\n

      Not sure what to ask? Here\u2019s a template that can help you get started:<\/p>\n \t\t\t<\/div>\n \t\t<\/div>\n \t<\/div>\n <\/div>\n<\/div>\n\n\n\n\n\t

      \n
      \n \t
      \n \t\t
      \n \t\t\t
      \n \t\t\t\t

       <\/p>\n

      Hi there!<\/p>\n

      As you may know, we\u2019re looking at migrating from {name of current ESP}\u00a0 in the coming months. Do you currently use {name of current ESP} on a regular basis? If you do, I need your help to evaluate ESPs and if we decide to move, make it as seamless and painless as possible. I\u2019d like to understand how you currently use {name of current ESP}. For example:<\/p>\n