0% found this document useful (0 votes)
101 views2 pages

Appriver

Uploaded by

vevipar729
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
101 views2 pages

Appriver

Uploaded by

vevipar729
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

In-Telecom- Migration from Appriver to Office 365

Scope:

The scope of the project is limited to:

 Migration from Appriver service to Office 365


 Review and update SPF/DKIM/DMARC.
 Setup MFA and SSPR (Self Service Password Reset) for users on Office 365.
 Documentation.

Pre-requisites (required before the start of the project):

 Global Admin access to Office 365 Tenant and Licenses.


 Access to Public DNS management credentials.
 Access to AppRiver mailbox management portal.
o Admin account with valid mailbox.
o BitTitan MigrationWiz licenses (User Migration Bundle) x 39 (Per mailbox)
o No. of distribution lists to be migrated.
 List of mailboxes considered for migration with size.
 Information about any existing devices or applications dependent on source services for
mail relay.
 Information about any existing DL’s in use.
 Information about email client in use with version.

Deliverables:

 Migrate Mailboxes & DLs from Appriver to Office 365.


 Review and update SPF/DKIM/DMARC.
 Setup MFA and SSPR (Self Service Password Reset) for users on Office 365.
 Documentation.

Points Confirmed:

 Exchange is hosted in AppRiver.


 Total number of mailboxes to be migrated = 39
 All end users’ machines are running with the latest windows patches.
 No Auditing, Retention and litigation hold policies are in place.
 No public folders are present.
 Mailbox data to be migrated is from source services only, no local data is required to be
migrated for OneDrive, SharePoint, and Teams data to be migrated.
 Destination O365 tenant setup will be cloud only.

Assumptions:

 No Domain controller exists.


 All user identities will be cloud only in O365.
 ITBD will setup O365 tenant and domain registration.
 Only one public domain exists that needs to be added to the new 365 tenant.
 Assuming the data size is below 50GB for each mailbox.
 EOP (Exchange Online Protection) will be in use.
 End user support will be taken care of by In-Telecom.

Key Activities:

 Review current source service setup: - 05


o Current AppRiver Portal.
o Office 365 Tenant setup.
o Domain registration.
o User identity creation.
 Validation of dependent device and third-party applications for relay 02
 Review and Setup Office 365 tenant and licenses. 02
 Prepare source user environment to migrate to O365 05
 Perform Pre-staging migration for users 05
 Perform Full Migration for users 05
 Review and update DNS (Internal / External) for SPF / DKIM and DMARC 03
records.
 Implement EOP configuration 01
 Mail flow cutover and testing 02
 Review and Setup DLs, alias, groups, and forwarders. 03
 Enable MFA and SSPR for all users. 02
 Setup relay for dependent devices/third party applications 01
 End user documentation – How to configure outlook profile? 02
 Documentation 02
Total 40

You might also like