Office 365: Everything You Wanted to Know How to Use this Document?


Migrate your Org’s data to Office 365 Enterprise



Download 0.81 Mb.
Page32/39
Date20.06.2017
Size0.81 Mb.
#21123
1   ...   28   29   30   31   32   33   34   35   ...   39

Migrate your Org’s data to Office 365 Enterprise


When you migrate an enterprise organization to Office 365, it's important to plan exactly what steps you want to take, when to perform them, and who will perform them.

Migrate email to Office 365


Your organization can migrate email to Office 365 from other systems.

Migrate mailboxes from Exchange Server


For migrations from an existing on-premises Exchange Server environment, an administrator can migrate all email, calendar, and contacts from user mailboxes to Office 365.


Use Office 365 Import Service to migrate PST-files


If your organization has many large PST files, you can use the Office 365 Import Service to migrate email data to Office 365.


Migrate email from another IMAP-enabled email system


You can use the Internet Message Access Protocol (IMAP) to migrate user email from Gmail, Exchange, and other email systems that support IMAP migration. When you migrate the user's email by using IMAP migration, only the items in the users' inbox or other mail folders are migrated. Contacts, calendar items, and tasks can't be migrated with IMAP, but they can be by a user.


Have users import their own email


Users can import their own email, contacts, and other mailbox information to Office 365. See Migrate email and contacts to Office 365 for Business to learn how.


Migrate files and folders


Before deciding on a migration strategy, it is vital that you perform an analysis of your current environment. This analysis should focus on those SharePoint workloads and content that you plan to move to SharePoint Online.

Office 365 provides the following methods for migrating multiple files to SharePoint Online.



  • Use Microsoft's Fast Track service for tools and guidance to get your data migrated to the cloud.

  • You can use the SPO migration API can be used to create migration import job to Office 365 and queue it up for later processing by a separate timer job.

  • Use Windows PowerShell cmdlets for SPO Migration Public Preview to migrate content from an on-premises fileshare or an on-premises SharePoint Server site to Office 365.

Microsoft partners are also available to assist with migrating your SharePoint content to SharePoint Online using third-party tools. Before choosing the migration tool to migrate your SharePoint content, be sure to verify that the tool meets your migration requirements and that it supports all of the SharePoint artifacts you want to migrate.

Move your OneDrive files from SharePoint 2013 to Office 365


Moving to OneDrive for Business on Office 365 involves a few one-time tasks. To move your files, do the following tasks in sequence:



  1. Go to your SharePoint OneDrive for Business library

  2. Sync your SharePoint Server 2013 OneDrive for Business library to your computer

  3. Create a backup copy of the synced library folder on your computer

  4. Stop syncing your SharePoint Server 2013 OneDrive for Business library

  5. Sync your Office 365 OneDrive for Business library to your computer

  6. Upload files to your synced Office 365 OneDrive for Business library

Note: Files you move from SharePoint Server 2013 to Office 365 don’t retain their original metadata and, they are essentially recognized as new files. As a result, these files don’t retain metadata details such as Modified and Modified By.

Also, refer to: Migrate OneDrive for Business document library files from on-premises SharePoint 2013 to Office 365 article.


Resources


  • Import PST files or SharePoint data to Office 365

  • Encrypt and import PST files to Office 365 (network upload)

  • Import unencrypted PST files to Office 365 (network upload)

  • Use drive shipping to import PST files to Office 365 (drive shipping)

  • Import SharePoint data to Office 365 (network upload and drive shipping)

Migrate Skype for Business users


Learn how to migrate user settings and move users to Skype for Business Online in the Move users to Skype for Business Online article.

  • Before actually moving the user to Office 365, you should first confirm that the user accounts are synchronized to the cloud, and assign them a license.

  • Before you start migrating users to Skype for Business Online, you should backup the user data associated with the accounts to be moved.

  • Before you begin to move users to Skype for Business Online, you may want to move a few pilot users to confirm that your environment is correctly configured. You can then verify that the features and services function as expected before attempting to move additional users.

  • You can verify that the user was moved successfully by checking online user settings and features.


Archiving third-party data


Office 365 has released a new feature that lets you import and archive third-party data from social media platforms, instant messaging platforms, and document collaboration platforms, to mailboxes in your Office 365 organization. Examples of third-party data sources that you can import to Office 365 include the following:

  • Social: Twitter, Facebook, Yammer, and LinkedIn

  • Instant messaging: Yahoo Messenger, GoogleTalk, and Cisco Jabber

  • Document collaboration: Box and DropBox

  • Vertical industries: Customer Relationship Management (such as Salesforce Chatter) and Financials (such as Thomson Reuters and Bloomberg)

  • SMS/text messaging: BlackBerry

After third-party data is imported, you can apply Office 365 compliance features to this data.

The following illustration and description explain how the third-party data import process works.





  1. Customer works with their partner of choice to configure a connector that will extract items from the third-party data source and then import those items to Office 365.

  2. The partner connector connects to third-party data sources via a third-party API (on a scheduled or as-configured basis) and extracts items from the data source. The partner connector converts the content of an item to an email message format.

  3. Partner connector connects to the Azure service in Office 365 by using Exchange Web Service (EWS) via a well-known end point.

  4. Items are imported into the mailbox of a specific user or into a "catch-all" third-party data mailbox. Whether an item is imported into a specific user mailbox or to the third-party data mailbox is based on the following criteria:

  1. Items that have a user ID that corresponds to an Office 365 user account. If the partner connector can map the user ID of the item in the third-party data source to a specific user ID in Office 365, the item is copied to the Purges folder in the user's Recoverable Items folder. Users can't access items in the Purges folder. However, you can use Office 365 eDiscovery tools to search for items in the Purges folder.

  2. Items that don’t have a user ID that corresponds to an Office 365 user account. If the partner connector can't map the user ID of an item to a specific user ID in Office 365, the item is copied to the Inbox folder of the third-party data mailbox. Importing items to the inbox allows you or someone in your organization to sign in to the third-party mailbox to view and manage these items, and see if any adjustments need to be made in the partner connector configuration.

Resources


  • Archiving third-party data in Office 365

  • Enable or disable archive mailboxes in Exchange Online

  • Place a mailbox on Litigation Hold

  • Create or remove an In-Place Hold


1   ...   28   29   30   31   32   33   34   35   ...   39




The database is protected by copyright ©ininet.org 2024
send message

    Main page