Google Apps for Work - Manual (Page 50)

Phase 1: Core IT
50
“We left the old world behind. We did
not migrate mail or calendar. We gave
people instructions on how to migrate
contacts. We gave instructions on how
to archive mail to a local file.”
—Wietze Devries, Principal IT
Architect, MeadWestvaco
MeadWestvaco is a packaging company
based in the United States. It has 15,000
Google Apps users.
Assess company-wide change impacts | How to
To get started, create a table where you’ll track your change impacts.
Identify the owners for these changes, what the solution looks like and
which change management activities—training, communications, internal
updates—might be needed to support it.
You’ll continue to track these items throughout your deployment and
execute your communications and training through Go-Live.
Change impact
Impact
level
Solution Change management needs
Authentication High Users will need to log in
to the main Google
Apps web login (either
gmail.com or
mail.domain.com) Communications: Promote new login process through
emails leading up to Go-Live.
Training: Include demo of new login in basic Google Apps
training. Update the Getting Started guide with
instructions for logging into Google Apps and distribute
guides at Go-Live.
Browser access High Users will use Google
Chrome to access
Google Apps Communications: Promote the Chrome browser as part
of the switch to Google Apps.
Training: Point out the Chrome page on the user learning
center, which shows new features and how to import
bookmarks. Include information in the basic Google
Apps training classes.
Legacy email
access High Users can access their
legacy email for three
months and can send/
receive email Communications: Include information about legacy
email access in migration reminders. Send reminder
messages every week one month before the legacy email
system is retired.