Follow these directions if you are transitioning off an existing email service onto the Iterable platform. This is assuming you will be importing users into Iterable through the UI with CSV list uploads.
1. Export all users from your existing email service. If you were using Mailchimp, you will need to export all lists, since Mailchimp does not have the concept of a master list that includes all users across all lists.
Performing the list import above will load your subscribers into Iterable, establishing user profiles for them if they do not yet exist in your deployment.
3. Export all hard bounces and unsubscribes from your existing service. Hard bounces are old, outdated or misspelled email addresses that are no longer in use.
4. In Iterable, channel unsubscribe hard bounced and unsubscribed emails by going to Users > Lists > Channel Unsubscribe Users.
From here, you'll be able to select the channels that you want to unsubscribe these users from. Unsubscribe them from all channels if you do not want them to receive any communication from you. Unsubscribe them from just the marketing channels if you do not want them to receive any promotional messages, but still want them to receive transactional messages.
As with our List Import functionality, you can enter your hard bounced and unsubscribed users into a free text field (like above) or you can pull them from a CSV on your computer. The above setup will unsubscribe a single user (email@example.com) from the Push Marketing Channel, but you can also do this for multiple channels and users simultaneously (if wanting to unsubscribe the same list of users from the same channels).
You can also toggle "Trigger workflows from this list?" on if you'd like to pass the users through any pre-existing "Unsubscribed from Channel" workflows.
5. Click "Remove subscribers" and you're done! These users will no longer be subscribed to the selected channels.