Email migration: Difference between revisions
Content deleted Content added
Reverted 1 edit by 111.125.136.70 (talk): == promotional content (TW) |
copy edit |
||
| Line 1: | Line 1: | ||
'''Email Migration''' is a process in which an [[email]] or multiple email messages are migrated from one [[email client]] to another email client. An equivalent term is '''Mailbox Migration''', in which case records such as e-mails, appointments, contacts or tasks may also be migrated. In general, email migration is required when a user is switching from its current email client to a new one. Usually email clients don't support similar file formats for saving mailbox data. |
'''Email Migration''' is a process in which an [[email]] or multiple email messages are migrated from one [[email client]] to another email client. An equivalent term is '''Mailbox Migration''', in which case records such as e-mails, appointments, contacts or tasks may also be migrated. In general, email migration is required when a user is switching from its current email client to a new one. Usually, email clients don't support similar file formats for saving mailbox data.<ref>{{Cite web|title=Simplified, Risk-Free Office 365 and G Suite Tenant Migration|url=https://www.duocircle.com/email/tenant-migration|date=2020-04-23|website=DuoCircle|language=en-US|access-date=2020-05-20}}</ref> |
||
== Scenarios == |
== Scenarios == |
||
Mailboxes may be migrated for different reasons.<ref>Nagourney, Adam [http://thecaucus.blogs.nytimes.com/2009/01/19/and-you-thought-you-had-e-mail-problems/] New York Times, January 19, 2009</ref> For example, mailboxes may need to be migrated because a company wants to use a new email [[service provider]]. Or mailboxes may need to be migrated following a company [[takeover|acquisition]] or [[merger]]. In most cases, a simple one-time migration approach may be employed. However, more advanced scenarios exist, including: |
Mailboxes may be migrated for different reasons.<ref>Nagourney, Adam [http://thecaucus.blogs.nytimes.com/2009/01/19/and-you-thought-you-had-e-mail-problems/] New York Times, January 19, 2009, </ref> For example, mailboxes may need to be migrated because a company wants to use a new email [[service provider]]. Or mailboxes may need to be migrated following a company [[takeover|acquisition]] or [[merger]]. In most cases, a simple one-time migration approach may be employed. However, more advanced scenarios exist, including: |
||
* Consolidation: email migration is performed to consolidate multiple accounts into one, for example following an employee's departure. |
* Consolidation: email migration is performed to consolidate multiple accounts into one, for example following an employee's departure. |
||
* Backup: email migration is performed to back up or preserve data, for example to ensure legal [[Regulatory compliance|compliance]]. |
* Backup: email migration is performed to back up or preserve data, for example, to ensure legal [[Regulatory compliance|compliance]]. |
||
* Coexistence: email migration is performed for evaluation purposes, for example during a migration pilot. |
* Coexistence: email migration is performed for evaluation purposes, for example during a migration pilot. |
||
* Upgrade: email migration is performed to facilitate an [[upgrade]], for example when deploying a new version of an email system. |
* Upgrade: email migration is performed to facilitate an [[upgrade]], for example when deploying a new version of an email system. |
||
| Line 14: | Line 14: | ||
* Content conversion: this allows content to be converted, for example from [[TNEF]] to [[MIME]] format. |
* Content conversion: this allows content to be converted, for example from [[TNEF]] to [[MIME]] format. |
||
* Property mapping: this allows properties to be mapped, for example from [[Gmail]] to [[Microsoft Exchange Server|Exchange]] contacts. |
* Property mapping: this allows properties to be mapped, for example from [[Gmail]] to [[Microsoft Exchange Server|Exchange]] contacts. |
||
* Copy Email: Make a copy of email from a source mailbox to a destination mailbox |
* Copy Email: Make a copy of an email from a source mailbox to a destination mailbox |
||
== Features == |
== Features == |
||
Email migration solutions may implement different features which |
Email migration solutions may implement different features which determine their suitability for different migration scenarios: |
||
* Supported systems: defines the list of source and destination systems supported (ex: [[IMAP]], [[Gmail]], [[Microsoft Exchange Server|Exchange]]). |
* Supported systems: defines the list of source and destination systems supported (ex: [[IMAP]], [[Gmail]], [[Microsoft Exchange Server|Exchange]]). |
||
* Administrative logins: allows administrative login to multiple user mailboxes (ex: using [[OAuth]]). |
* Administrative logins: allows administrative login to multiple user mailboxes (ex: using [[OAuth]]). |
||
* Multi-pass migrations: allows multiple |
* Multi-pass migrations: allows multiple migrations pass without creating duplicates. |
||
* Scalability: allows a large set of mailboxes to be migrated concurrently. |
* Scalability: allows a large set of mailboxes to be migrated concurrently. |
||
* Monitoring: allows administrators to monitor migration progress and receive alerts. |
* Monitoring: allows administrators to monitor migration progress and receive alerts. |
||
Revision as of 09:05, 20 May 2020
Email Migration is a process in which an email or multiple email messages are migrated from one email client to another email client. An equivalent term is Mailbox Migration, in which case records such as e-mails, appointments, contacts or tasks may also be migrated. In general, email migration is required when a user is switching from its current email client to a new one. Usually, email clients don't support similar file formats for saving mailbox data.[1]
Scenarios
Mailboxes may be migrated for different reasons.[2] For example, mailboxes may need to be migrated because a company wants to use a new email service provider. Or mailboxes may need to be migrated following a company acquisition or merger. In most cases, a simple one-time migration approach may be employed. However, more advanced scenarios exist, including:
- Consolidation: email migration is performed to consolidate multiple accounts into one, for example following an employee's departure.
- Backup: email migration is performed to back up or preserve data, for example, to ensure legal compliance.
- Coexistence: email migration is performed for evaluation purposes, for example during a migration pilot.
- Upgrade: email migration is performed to facilitate an upgrade, for example when deploying a new version of an email system.
Procedure
Various technical procedures are normally used to achieve email migration:
- Email forwarding: this allows a mailbox to forward received content to a designated email address.
- MX record modification: this allows a mail server to process emails on behalf of a designated SMTP domain.
- Content conversion: this allows content to be converted, for example from TNEF to MIME format.
- Property mapping: this allows properties to be mapped, for example from Gmail to Exchange contacts.
- Copy Email: Make a copy of an email from a source mailbox to a destination mailbox
Features
Email migration solutions may implement different features which determine their suitability for different migration scenarios:
- Supported systems: defines the list of source and destination systems supported (ex: IMAP, Gmail, Exchange).
- Administrative logins: allows administrative login to multiple user mailboxes (ex: using OAuth).
- Multi-pass migrations: allows multiple migrations pass without creating duplicates.
- Scalability: allows a large set of mailboxes to be migrated concurrently.
- Monitoring: allows administrators to monitor migration progress and receive alerts.
- Analytics: allows administrators to access statistics such as transfer speed, error rate, etc.
- Reliability: allows the migration process to automatically handle or retry errors during migration.
- Filtering: allows migration of specific content (ex: date range) from specific locations (ex: folders).
- Security: allows migrated content to remain secure, for example using SSL encryption.
See also
References
- ^ "Simplified, Risk-Free Office 365 and G Suite Tenant Migration". DuoCircle. 2020-04-23. Retrieved 2020-05-20.
- ^ Nagourney, Adam [1] New York Times, January 19, 2009,