Support most email providers / servers on the market • Cost effective and scalable YippieMove offers (in addition to consulting) • Single-user migrations • Batch migrations • Self-service portals • API
or multiple domains? • If large migration, can it be broken down into groups? • Do you have access to make DNS changes? • What is the TTL for the relevant DNS-records? • Do you have access to email administration? • Both source and destination
email today? • Where are the messages stored (remote or locally)? • How can we access the messages? • What authentication methods are supported? • When is the lowest email transaction volume? • What about contacts and calendar?
the TTLs to the lowest value (usually 3600s/1h) • Prepare a list of all users, domains and aliases The week of the migration • Setup all accounts on the destination • Conﬁgure all domain and user aliases • Send out provisioned destination passwords to users
business hours) • Change the DNS-records (MX and others) • Provision new source passwords • Assuming no other method is supported A few hours later (4xTTL is a good rule of thumb) • Begin the email migration
for authentication when possible • Use application-speciﬁc password as fallback • TTLs can’t be trusted • Don’t provide users with the reseted password • They will change the password • It will lead to interruptions in the migration