Migrating to the AppRiver Hosted Exchange Platform

Purpose:
To provide basic guidelines for migration to AppRiver’s Hosted Exchange Platform.

Clarifications:
This guideline provides a high-level overview of migration processes to AppRiver’s Hosted Exchange Platform and is by no means exhaustive. One or more of these processes may or may not work with your current environment including, but not limited to, your current mail host, DNS provider, and domain name registrar.

Note: Please consult with your Sales Engineer for migration details.

There are three primary methods to migrate a live domain (actively sending and receiving mail) to AppRiver’s Hosted Exchange environment. These three methods are listed below. The Environments Supported section defines a best migration path for the listed platforms. The terms utilized below are designed to be generic and encompassing of multiple generations of technology. Please consult with your Sales Engineer about a specific solution if you have any questions.

Definitions:

  • Local Server – Defined as any server that manages mail for the client and is physically controlled by the client, either at their current location or a branch office.

  • Hosted POP3/IMAP Server – Clients mail is hosted by a 3rd party company and is limited to POP/IMAP connections. 

  • Hosted Exchange Server – Defined as an Exchange service hosted by a 3rd party company. The client has no direct control over the server.


QUICK START MIGRATION SETUP TO APPRIVER
 

A. Split Domain Routing

Environments Supported:

  • Local Server (Exchange, Domino, Lotus Notes, iMail, POP/IMAP)

  • Hosted POP3/IMAP Server *limited

Migration Path:

1. *If this is a Hosted POP3/IMAP Server, verify with your current mail host first that they will accept mail for your domain when the MX Records do not point at their mail server directly. If you are unable to verify this with your current provider, please contact your AppRiver Sales Engineer about how to proceed with this procedure.

2. Enable domain routing service in the Customer Portal.

3. Provide an IP/Hostname address for the existing mail server. Alternatively the primary MX Record can be used to deliver as well.

4. Test the relay connection between the AppRiver Exchange Server and existing mail host. The recipient of your test should receive a simple email confirming the test was successful.

5. If the mail is hosted locally, verify SMTP is not limited to a specific IP, if so, add the IP range of the AppRiver Hosted Exchange Server to the device limiting SMTP traffic. This IP range can be found in the Customer Portal.

6. When a successful test has been verified, existing MX Records and CNAME Record can be removed and replaced with those supplied by AppRiver.

7. Allow 24 hours for domestic email and 48 hours for international email to be re-routed to AppRiver’s Hosted Exchange Server before creating any mailboxes in the Customer Portal.

8. Follow the existing setup procedures for mailbox creation and mail client setup after the allotted time period has passed.

9. Follow the existing procedures for importing mail to the AppRiver Hosted Exchange Server.

10. After all users have been migrated from the previous mail host to the AppRiver Exchange Server, disable domain routing to avoid reoccurring billing. This feature is normally a billable service but free of charge during a 30-day trial.

B. Mail Forwarding

Environments Supported:

  • Local Server (Exchange, Domino, Lotus Notes, POP)

  • Hosted Exchange Server

  • Hosted POP3/IMAP Server

Migration Path:

1. Enable domain routing service in the Customer Portal. Use the primary MX Record as the alternate email server to deliver mail. 

2. Create one or more user accounts, including all alias email addresses with Exchange Service in the AppRiver Customer Portal.

3. From the control panel of the existing mail host, forward each account that will be moving to the AppRiver Hosted Exchange Server to the users System Address provided in the Customer Portal for each mailbox.

4. Follow existing procedures for mail client setup and importing mail to the AppRiver Hosted Exchange Server.

5. Create all Group Distribution Lists, Foreign Contacts and Resource Mailboxes in the Customer Portal Exchange interface.

6. After all users have been setup on the AppRiver Customer portal, access the control panel of the previous mail host. Existing MX Records and CNAME Record can be removed and replaced with those supplied by AppRiver.

7. After all users have been migrated from the previous mail host to the AppRiver Exchange Server, disable domain routing to avoid reoccurring billing. This feature is normally a billable service but free of charge during a 30-day trial.

 

C. Hot Cut

Environments Supported:

  • Local Server (Exchange, Domino, Lotus Notes, POP)

  • Hosted Exchange Server

  • Hosted POP3/IMAP Server

Migration Path:

1. Create all user accounts, including alias email addresses in the AppRiver Customer Portal with Exchange Service.

2. Create all Group Distribution Lists, Foreign Contacts and Resource Mailboxes in the Customer Portal Exchange interface.

3. From the control panel of the existing mail host, existing MX Records and CNAME Record may be removed and replaced with those supplied by AppRiver.

NOTE: DNS Records can take up to 24 hours to update across the US and 48 hours internationally before all mail is routed to AppRiver.

4. Optional – From the control panel of the existing mail host, forward each account that is moving to the AppRiver Hosted Exchange Server to the users System Address provided in the Customer Portal for each mailbox.

5. Follow normal procedures for mail client setup and importing mail to the AppRiver Hosted Exchange Server


D. AppRiver Support & Contact Information

For future reference, AppRiver Sales Engineers may be reached via email at
se@appriver.com or by phone 850-932-5338 x2474.

  • Standard Implementation Support – Standard Implementation Support is provided during normal business hours, or 7-7pm CST, Monday through Friday.

  • After-Hours/Weekend Implementation Support – After-hours implementation support must be pre-arranged with your Sales Engineer team.

  • Technical Support – Technical support is provided 24 x 7 x 365 by way of AppRiver's ticketing system.  24 x 7 x 365 phone support requires a ticket number for reference.

Add Feedback