BPOS to Office 365 Migration Planning

November 8, 2011  |  No Comments  |  by matkordell@cyberstreams.com   |  Blog, News

Updates on Migrating from BPOS to Office 365

The emails for BPOS migration notification window times have started flying out of Microsoft. What follows will attempt to cover a broad overview of the topics regarding the migration from BPOS to Office 365.

For more granular questions, please visit our BPOS to Office 365 Migration FAQ.

What Changes?

New Server Platform

  • Exchange 2010, SharePoint 2010, Lync 2010
  • Architected from the ground up for multi-tenancy
  • Server-service parity
  • Improved coexistence
  • Native migration tools

Improved Administration

  • Role-based access control
  • Extended control panels
  • Self-serve user admin
  • More settings / options exposed to admin
  • Delegated admin capabilities

New Identity Platform

  • Single sign-on (SSO)
  • Federated identity
  • Live ID infrastructure
  • No more BPOS sign-in client
  • Microsoft Federation Gateway

New System Requirements:

Changes Only (for a full list of supported platforms, read your service agreement):

  • Office Client: Must have Office 2007 SP2 or Office 2010 (any)
  • Internet Explorer: IE 7 or higher required
  • Instant Messaging: Lync 2010 required (OCS is no longer supported)
  • Service Connector: BPOS sign-in app is no longer supported.
  • Desktop: Install Microsoft Online Desktop Upgrade to sync services.
  • Passwords: There are new password requirements that will need to be met (some users may already meet these).

Transition Timeline:

Q3 2011

Q4 2011

Q1 2012

Q2 2012

Q3 2012

Office 365 Available

All customers can transition except BES users, users > 20,000 SharePoint seats, and Education users

All users can transition, except Education

All users can transition

Transition ends

>>>> All BPOS customers must transition to Office 365 by Sep 2012. <<<<

Roles and Responsibilities:


  • Co-ordinate transition planning discussions
  • Update desktops
  • Communicate to end users

Microsoft Partners

  • Drive transition planning discussions
  • Support transition plan
  • Provide deployment assistance
  • Offer training


  • Drive Awareness
  • Set scheduling
  • Migrate back-end data

Scheduling Timeline:

90 Days Prior:

  • Microsoft: Send “Readiness Survey” to account team contacts.
  • Customer/Partner: Customer states preferred date, understand readiness prerequisites.

60 Days Prior:

  • Microsoft: Send “Be ready by date”.
  • Customer/Partner: Transition plan, prepare desktops and deploy Lync.

30 Days Prior:

  • Microsoft: Send “date range” for transition.
  • Customer/Partner: Ensure all end users meet all requirements.

14 Days Prior:

  • Microsoft: Send “Exact transition date”.
  • Customer/Partner: Notify end users on steps to reconnect after transition.

2 Days Prior:

  • Microsoft: Send email to notify “Locked time”.
  • Customer/Partner: MS Online Admin console is locked.

Transition Complete

  • Microsoft: Send email to notify of completion.
  • Customer/Partner: Respond to completion survey.

Transition Process:

Plan and Prepare:

  • Learn about transition and new identity and single sign-on options
  • Schedule
  • Deploy end-user software
  • Prepare end-users
  • Pilot (Midsize and Enterprise organizations)

Transition :

  • 48 hours
  • Uninterrupted mail flow
  • Admin and customer portal locked
  • SharePoint locked for part of weekend


  • Configure computers and devices
  • Re-configure mail-enabled applications

New Deployment:

  • Deploy new services or users
  • Deploy ADFS, Single Sign-On, Rich Co-existence, or Exchange CAS

Mapping Plans:


New Office 365 Plan


Office 365 E1

Exchange Online

Office 365 Exchange Plan 1

Exchange Online Deskless

Office 365 Exchange Kiosk

SharePoint Online

Office 365 SharePoint Plan 1

Office Communications

Office 365 Lync Plan 1

Office Live Meeting

Office 365 Lync Plan 2

Return to Office 365 Advisors Homepage

Posted in Blog, News and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *