<?xml version="1.0" encoding="ISO-8859-1"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Migrating Your List? Remember To Tell Them&#8230;</title>
	<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm</link>
	<description>Email Marketing Tips on the AWeber Blog</description>
	<pubDate>Fri, 16 May 2008 22:49:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Justin Premick</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19810</link>
		<dc:creator>Justin Premick</dc:creator>
		<pubDate>Mon, 17 Dec 2007 14:59:07 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19810</guid>
		<description>Hilary,

Exactly - we maintain an internal list of domains and addresses that shouldn't be on any email list.

We can then compare imports to it to gauge whether or not the imported list appears to have been properly managed.

While this isn't the only criteria we use to evaluate imports - our Customer Solutions Team manually reviews them as well - it's one of a number of automated measures that help us to maximize all users' email deliverability.

Thanks much also for your feedback on how we might improve the imports page - I can see how that could help make transitioning to AWeber even smoother - and we certainly want to do that :)</description>
		<content:encoded><![CDATA[<p>Hilary,</p>
<p>Exactly - we maintain an internal list of domains and addresses that shouldn&#8217;t be on any email list.</p>
<p>We can then compare imports to it to gauge whether or not the imported list appears to have been properly managed.</p>
<p>While this isn&#8217;t the only criteria we use to evaluate imports - our Customer Solutions Team manually reviews them as well - it&#8217;s one of a number of automated measures that help us to maximize all users&#8217; email deliverability.</p>
<p>Thanks much also for your feedback on how we might improve the imports page - I can see how that could help make transitioning to AWeber even smoother - and we certainly want to do that <img src='http://www.aweber.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hilary</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19799</link>
		<dc:creator>Hilary</dc:creator>
		<pubDate>Sun, 16 Dec 2007 19:04:43 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19799</guid>
		<description>I think they can recognise some addresses as defunct without emailing them, eg because the ISP's gone out of business. Then if there are too many of these, they conclude that there will be lots of other defunct addresses in the list that they can't identify, and so they reject the whole lot. It makes sense.</description>
		<content:encoded><![CDATA[<p>I think they can recognise some addresses as defunct without emailing them, eg because the ISP&#8217;s gone out of business. Then if there are too many of these, they conclude that there will be lots of other defunct addresses in the list that they can&#8217;t identify, and so they reject the whole lot. It makes sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lori Titus</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19798</link>
		<dc:creator>Lori Titus</dc:creator>
		<pubDate>Sun, 16 Dec 2007 18:50:33 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19798</guid>
		<description>I am confused - if aWeber can identify a portion of a list as &#34;undeliverable&#34; when uploading, why not tell the system to not upload those email addresses?  Or is aWeber finding this out by emailing each address while uploading?</description>
		<content:encoded><![CDATA[<p>I am confused - if aWeber can identify a portion of a list as &quot;undeliverable&quot; when uploading, why not tell the system to not upload those email addresses?  Or is aWeber finding this out by emailing each address while uploading?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hilary</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19580</link>
		<dc:creator>Hilary</dc:creator>
		<pubDate>Tue, 11 Dec 2007 22:04:57 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19580</guid>
		<description>Hi Justin,

Thanks for the detailed reply. I do understand why Aweber wouldn't want to import a list with too many undeliverables, and I see what you mean about 'cleaning'. I have a lot of respect for your firmness on this - I moved to Aweber for its better delivery rates, after all. :)

The only reason I had a problem with the changeover was that I had no advance warning that I might not be able to import my list. Since I followed exactly the kind of procedure you suggest in your post, I had a lot of confused people waiting for a confirmation email I'd told them to expect, but couldn't send. To clarify, I didn't send them a 'reminder'; I had to send them an alternative way to sign up, and an apology for the mess!

So a simple note in the help files would save your new customers this kind of embarrassment. Something like - 
&#34;If your list is old and hasn't been well managed, you may not be able to import any email addresses. If you're not sure whether your list will qualify to be imported...&#34;
... and then tell people how they can check whether it'll work, before they start following the (excellent) advice in your post.</description>
		<content:encoded><![CDATA[<p>Hi Justin,</p>
<p>Thanks for the detailed reply. I do understand why Aweber wouldn&#8217;t want to import a list with too many undeliverables, and I see what you mean about &#8216;cleaning&#8217;. I have a lot of respect for your firmness on this - I moved to Aweber for its better delivery rates, after all. <img src='http://www.aweber.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The only reason I had a problem with the changeover was that I had no advance warning that I might not be able to import my list. Since I followed exactly the kind of procedure you suggest in your post, I had a lot of confused people waiting for a confirmation email I&#8217;d told them to expect, but couldn&#8217;t send. To clarify, I didn&#8217;t send them a &#8216;reminder&#8217;; I had to send them an alternative way to sign up, and an apology for the mess!</p>
<p>So a simple note in the help files would save your new customers this kind of embarrassment. Something like -<br />
&quot;If your list is old and hasn&#8217;t been well managed, you may not be able to import any email addresses. If you&#8217;re not sure whether your list will qualify to be imported&#8230;&quot;<br />
&#8230; and then tell people how they can check whether it&#8217;ll work, before they start following the (excellent) advice in your post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Premick</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19579</link>
		<dc:creator>Justin Premick</dc:creator>
		<pubDate>Tue, 11 Dec 2007 20:58:04 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19579</guid>
		<description>Hi Hilary,

While I disgree with your advice to our readers, I appreciate you sharing your experience. Not only will it give me a few things to think about modifying in our help materials, but it also brings up the importance of proper list management.

ISPs look at many factors when determining whether to deliver email from a sender to the inbox or bulk folder (or neither), and your bounce rate is one of those factors. An email solution that doesn't automatically manage/remove undeliverables will cause issues not only while using them, but if/when you ever decide to move your list elsewhere (as you've noted).

&#34;Cleaning&#34; a list would involve emailing the list, in which case you risk the same bounces you'd be looking to avoid. While an email service such as ours may be able to identify some known &#34;dead&#34; addresses in advance and prevent those from being emailed, it won't know all of them. &#34;Cleaning&#34; is just not something we can in good faith recommend, because of the potential damage to your deliverability that goes along with it.

Sending a reminder, while it appears to have helped in this specific scenario, isn't something we advise either, because of the high risk of spam complaints - and accusations that you're not truly using a Confirmed Opt-In model, like in an &lt;a href="/blog/email-deliverability/learning-to-let-go.htm" rel="nofollow"&gt;example discussed on this blog.&lt;/a&gt;

---

Picking an email marketing solution is an important decision for any business. No matter whether you end up going with AWeber or another company, make sure you choose a solution that manages undeliverables, supports industry standards such as Confirmed Opt-In, and actually gets your email delivered.

The consequences of choosing a solution that leaves you with an improperly managed list can follow you, making migration more challenging. However, in the event of a list where bounces have been handled, I still feel the points made in this post are valid, as they do help smooth the transition from one email solution to another.</description>
		<content:encoded><![CDATA[<p>Hi Hilary,</p>
<p>While I disgree with your advice to our readers, I appreciate you sharing your experience. Not only will it give me a few things to think about modifying in our help materials, but it also brings up the importance of proper list management.</p>
<p>ISPs look at many factors when determining whether to deliver email from a sender to the inbox or bulk folder (or neither), and your bounce rate is one of those factors. An email solution that doesn&#8217;t automatically manage/remove undeliverables will cause issues not only while using them, but if/when you ever decide to move your list elsewhere (as you&#8217;ve noted).</p>
<p>&quot;Cleaning&quot; a list would involve emailing the list, in which case you risk the same bounces you&#8217;d be looking to avoid. While an email service such as ours may be able to identify some known &quot;dead&quot; addresses in advance and prevent those from being emailed, it won&#8217;t know all of them. &quot;Cleaning&quot; is just not something we can in good faith recommend, because of the potential damage to your deliverability that goes along with it.</p>
<p>Sending a reminder, while it appears to have helped in this specific scenario, isn&#8217;t something we advise either, because of the high risk of spam complaints - and accusations that you&#8217;re not truly using a Confirmed Opt-In model, like in an <a href="/blog/email-deliverability/learning-to-let-go.htm" rel="nofollow">example discussed on this blog.</a></p>
<p>&#8212;</p>
<p>Picking an email marketing solution is an important decision for any business. No matter whether you end up going with AWeber or another company, make sure you choose a solution that manages undeliverables, supports industry standards such as Confirmed Opt-In, and actually gets your email delivered.</p>
<p>The consequences of choosing a solution that leaves you with an improperly managed list can follow you, making migration more challenging. However, in the event of a list where bounces have been handled, I still feel the points made in this post are valid, as they do help smooth the transition from one email solution to another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ty Coughlin</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19565</link>
		<dc:creator>Ty Coughlin</dc:creator>
		<pubDate>Tue, 11 Dec 2007 16:07:17 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19565</guid>
		<description>Justin, you are RIGHT ON! 

If you respect your lists, your lists will respect and continue to do business with you!</description>
		<content:encoded><![CDATA[<p>Justin, you are RIGHT ON! </p>
<p>If you respect your lists, your lists will respect and continue to do business with you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hilary</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19546</link>
		<dc:creator>Hilary</dc:creator>
		<pubDate>Mon, 10 Dec 2007 22:58:43 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-19546</guid>
		<description>Tip to Aweber users from personal experience - and Justin or someone, it might be a nice idea to add this to the help system - do not tell your list to expect a confirmation email before you've successfully imported the list.

I made this mistake - and then when I tried to import the list to Aweber, I was told that too many of the emails on the list were defunct, and so *none* of the subscribers could be imported.

Of course Aweber doesn't want to send emails to defunct addresses - that's a Good Thing. So I asked for help removing the old addresses from the list. (Aweber's system had identified these, of course, but I didn't know which they were.) This was refused. I asked for advice on how to clean the list in general - again, nothing doing.

So I had a few thousand people waiting for a confirmation email I'd told them to look out for, and that I couldn't send. In the end I managed to import most of a more recent subset of my list, and had to send another message through my old system: if you didn't see the confirmation email, here's a link to a subscription form, sorry.

I had several emails from puzzled subscribers - I'm still getting them, months later - and naturally 'mislaid' many subscribers. I'd have done much better to forget about importing altogether, and simply ask my subscribers to sign up at a new subscription form. And if I'd just checked, first, whether I &lt;em&gt;could&lt;/em&gt; import my list, that's exactly what I would have done.

Moral of this story: first import your list into Aweber. Then when you know whether that's worked, use your old system to tell them how the changeover will work.</description>
		<content:encoded><![CDATA[<p>Tip to Aweber users from personal experience - and Justin or someone, it might be a nice idea to add this to the help system - do not tell your list to expect a confirmation email before you&#8217;ve successfully imported the list.</p>
<p>I made this mistake - and then when I tried to import the list to Aweber, I was told that too many of the emails on the list were defunct, and so *none* of the subscribers could be imported.</p>
<p>Of course Aweber doesn&#8217;t want to send emails to defunct addresses - that&#8217;s a Good Thing. So I asked for help removing the old addresses from the list. (Aweber&#8217;s system had identified these, of course, but I didn&#8217;t know which they were.) This was refused. I asked for advice on how to clean the list in general - again, nothing doing.</p>
<p>So I had a few thousand people waiting for a confirmation email I&#8217;d told them to look out for, and that I couldn&#8217;t send. In the end I managed to import most of a more recent subset of my list, and had to send another message through my old system: if you didn&#8217;t see the confirmation email, here&#8217;s a link to a subscription form, sorry.</p>
<p>I had several emails from puzzled subscribers - I&#8217;m still getting them, months later - and naturally &#8216;mislaid&#8217; many subscribers. I&#8217;d have done much better to forget about importing altogether, and simply ask my subscribers to sign up at a new subscription form. And if I&#8217;d just checked, first, whether I <em>could</em> import my list, that&#8217;s exactly what I would have done.</p>
<p>Moral of this story: first import your list into Aweber. Then when you know whether that&#8217;s worked, use your old system to tell them how the changeover will work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Premick</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-18751</link>
		<dc:creator>Justin Premick</dc:creator>
		<pubDate>Fri, 07 Dec 2007 16:22:58 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-18751</guid>
		<description>Aaron,

My pleasure - I'm glad it's more usable for you :)</description>
		<content:encoded><![CDATA[<p>Aaron,</p>
<p>My pleasure - I&#8217;m glad it&#8217;s more usable for you <img src='http://www.aweber.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-18741</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 07 Dec 2007 02:18:41 +0000</pubDate>
		<guid>http://www.aweber.com/blog/email-deliverability/tell-subscribers-when-migrating.htm#comment-18741</guid>
		<description>Justin, thanks for making the posts show up entirely in the window of the reader. It's much more user friendly this way.</description>
		<content:encoded><![CDATA[<p>Justin, thanks for making the posts show up entirely in the window of the reader. It&#8217;s much more user friendly this way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
