Project North Staggered Email Migration Plan

1. Project NorthStaggered Email Migration Plan

2. Project NorthOverall Objectives of Email Migration Planning • Minimize customer impact • Minimize customer actions required • Minimize customer communications • Minimize cost • Ensure that the Email migration plan can be developed and implemented in the required timeframes and to allow for appropriate acceptance testing

3. Project North - Base Email Migration Plan • Verizon expected to create a separate instance of its back-office in the Ft. Wayne Data Center to support SpinCo. The Separate instance will be placed into service on 3-27-10. The Transaction Closing is expected to occur on July 1, 2010. The Ft. Wayne Data Center will not include systems or platforms needed to enable/provision Email accounts post-close. • Verizon is to provide a single LDIF file layout and data extract on 2-28, 5-31 & 6-30 for both SpinCo and WV. The file layouts will be based on the updated Consumer & Business email platform of Jan 2010. Frontier to begin testing of their email platforms ability to support email accounts from Vz LDIF & IMAP data in March 2010. • It is projected that Verizon will have completed the migration of all SpinCo MSN and AOL customers over to Yahoo or Verizon.net email service by 4-1-10. • Vz responsible for sending all customer change-in-carrier communications pre-close (7-1). Frontier to provide Verizon with suggested message input for pre-exit customer communications based on their exit plans. Verizon customer communications to meet Terms of Service conditions (notice to be delivered to customer sixty days prior to close). • Verizon will create a 3rd party contract with Yahoo to support SpinCo’s continuation of Yahoo services to customers post exit. Yahoo must support a separate instance for SpinCo to integrate with the Ft. Wayne IT systems as of 3-27-10 • Frontier set-up a replicated email address on the Frontier email Platform for all of the SpinCo customers identified in the at-close extract. • Frontier is responsible for resolving all Email User ID’s that are duplicated between the Vz.net and Frontier.net customers. For example, both the current Vz.net and Frontier .net email systems have a user ID of Richard.Smith. • Frontier will use an IMAP tool to transfer Customer data from the Verizon email Platform to the Frontier Email Platform. • Verizon has agreed to forward customer email for 180 days post-close. • Frontier is responsible for notifying the customer and all appropriate Care and Support organizations of the plan to migrate customer email post close. • Verizon will create a “static link” on the Spinco 2.0 portal allow a customer to self-select and access the Frontier Email Servers. No Vz/VOL Single Sign-On (SSO) will be available as Frontier.net email will have a separate log-on mechanism.

4. Project North Frontier Request for “Staggered” Email Migration Frontier requests a “Phased” approach to Email migration whereby accounts remain active on the Verizon email servers until Frontier is able to replicate the account on their systems and IMAP the existing email profile & customer data onto their servers. “Staggered” approach to email migration is to be applied to both SpinCo and West Virginia

5. Project North - “Staggered” Email Migration Plan • Verizon email customers will continue to be provided “full and duplicate” service effective 7-1-10 and until the individual customers are IMAP migrated over to Frontier email systems. “Full and duplicate service is defined as the customer continuing to have the same access, email generation, email filing, email deletion, forwarding, address book features/capabilities, [vacation auto-reply?] etc. “At Close” there will be no ability for a user to create a new alias in the Vz/VOL hosted email service in the Valwood data center. • SpinCo customers being served by the My SpinCo 2.0 portal will continue Message Center integration by pointing to the separate/virtual instance of the Message Center in the Vz Valwood data center facility. • Note that as customers are IMAP migrated from Vz mail systems to Frontier mail systems, the SpinCo 2.0 portal will cease being a useful tool for email notification/status as the message center will no longer be receiving Frontier customer email traffic as a result of email forwarding implementation. 3. Effective at Close, email customers that attempt to change their username and/or password will not be able to do so because the SpinCo 2.0 Portal to the SpinCo instance of VIPR will not be interfaced to the Verizon Valwood data center. • After the customers are IMAP transferred from the Vz hosted email systems to the Frontier systems, the customers will then again have the ability to change user name and password. Frontier will be responsible for customer communications advising the customers that they will not be able to change user name and password between 7-1-10 and when they are IMAP transferred. 4. Frontier is responsible for the customer communications that notifies the individual email customers of the day and time of their email migration and any “dark period” they may experience. • It is anticipated that Frontier will IMAP access and transfer approximately 15K of email customers per day post exit and will require 90+ days to complete the migration of all SpinCo accounts. • Frontier will provide the Verizon Email Team details of the email account migration to allow for the daily setting of email forward for each individual account as it is migrated. Verizon will set the forwarding and then “freeze” the access to the individual customer email box. • The VIPR/UWP instance for SpinCo in Ft. Wayne along with all other duplicated IT systems will not have the capability of distinguishing if a customer has been IMAP migrated or not. Frontier will be responsible for addressing this limitation with respect to customer communications and customer support. • Frontier will drop Final Email into the customer’s Verizon email account stating that their email account has migrated and provide details about accessing their new Frontier Email box. • Frontier to Migrate Customers based on Priority • Verizon to provide Frontier with definition of the email accounts that have been “active” during the month prior to “at exit”. This is projected to be 300K – 400K accounts. Frontier is then to make these accounts priority for migration during the 30 days post exit. • Frontier is also to establish priority for migration on all WV, Yahoo, and duplicate user ID email accounts.

6. Project North - Verizon Email SME’s • Judi Blackwell – RGS SME • Susan Hutyra – Email PLM • Karen Meade – Email Choice PLM • Mike Steiner – Email Choice SME • Tim Nyce – ISP Provisioning SME • Anil Chintalapudi – ISP Provisioning SME • Tulasi Akepati – ISP Provisioning SME • Lisa Demack – Net Ops Manager Email • Boyd Christensen – Net Ops Email Messaging SME • Robert Francher – Net Ops Email Messaging SME • Jeremy Brown – Net Ops SpinCo SME • Keith Longabaugh – Net Ops West Virginia SME • Monna Roberson – VOL Legal • Karen Muscato – VOL Legal • David Neyman – IT PMO • Dave Halenda – IT PMO • Bruce King – RGS/BRD Manager • Kevin Kempel – Project North ISP Manager