1 / 24

SharePoint Content Migration Tools

DM305. SharePoint Content Migration Tools. Kimmo Forss Architect Microsoft Corporation. Studying the current environment and knowing the capabilities of the future environment.

lucus
Télécharger la présentation

SharePoint Content Migration Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DM305 SharePoint Content Migration Tools Kimmo Forss Architect Microsoft Corporation

  2. Studying the current environmentand knowing the capabilities of the future environment “know thy enemy and know thyself; in a hundred battles you will neverbe in peril. When you are ignorant of the enemy but know yourself, yourchances of winning or losing are equal. If ignorant both of your enemyand of yourself, you are certain in every battle to be in peril.” -- The Art of War. Sun Tzu

  3. Disclaimer • This session will only cover the tools from CodePlex • There are a nr of excellent 3rd party tools available as well

  4. Agenda • Migration Planning and Process • Content Migration Tools

  5. Keys to Success • People • Source system knowledge (System X) • Target system knowledge (SharePoint, Exchange, etc.) • Knowledge • Development • System X (db) APIs (extracting) • SharePoint, Exchange,… (Web Parts, etc.) • Knowledge management • How to structure the data • Commitment

  6. Planning • Application Migration vs Content Migration • Best Practice: Don’t try to migrate application logic • Create the new application to meet the today’s needs (not yesterday’s)

  7. Migration Steps • Step 1: Study existing environment • Step 2: Gap Analysis • Step 3: Planning and Implementing • Step 4: Export information • Step 5: Map identities and metadata • Step 6: Import information • Step 7: Manual cleanup

  8. Data Export • This includes exporting the data either to a known format or directly to the target system • Plan for a phased export and make the source data read-only after the export • If data is exported to a neutral format on the file system make sure that you have enough storage and that the information is secured

  9. Data ExportOptions

  10. SharePoint Content Migration Tools • http://www.codeplex.com/SPMigration

  11. History • Started as a joint venture with HP Services to move their SPS 2001 environment to SPS 2003 • Plan from day 1 was to create a Framework not a point solution • API exists for developers • Code exists on codeplex

  12. Architecture • 2 step process • Export of data to a common documented format • Import of data from that format • Benefits • This allows us to create extractors for multiple systems • This allows us to write tools to modify the data prior to the Import

  13. Migration using the tools

  14. Extractors • SPS 2003/WSS 2.0 • SPS 2001 • Exchange Public Folders • Lotus QuickPlace • File Shares • + customer projects

  15. What about the OOB tools? • OOB Tools • Work on a site collection level • Site structures are moved as is • All lists, libraries (including content) • No chance to rearrange/merge/limit data • Require upgrade definition files • SharePoint Migration Tools • Designed for fine grained content migration • Allows content re-organization • Promoting/demoting sites in the hierarchy • Changing Site Definitions • Merging lists/libraries

  16. Content Re-Organizer • This is a tool that allows you to modify the data prior to Importing it to SharePoint • Allows moving/renaming sites/lists/libraries

  17. Demo scenario • Customer has Project Site Collections (WSS 2.0) that because of data aggregation needs need to be moved into a single Site Collection • Customer has a site that need to be live whilst migrating (new content is added to the old 2003 environment whilst migration in progress) • Customer also has emails in Exchange that needs to be moved to the same Site Collection as the above data • 3 different document libraries need to be merged into one

  18. Content Migration Extravaganza demo

  19. Recap of the demo • Extraction part extracted the site collections from the 2003 environment • We edited the export manifest file and re-arranged the content • Extraction of Exchange data

  20. SharePoint Readiness Resources

  21. Post Event DVD brought to you courtesy of:

  22. SUBMIT AN EVALUATION For a chance to win an 8GB ZUNE! Submit evaluations on MySPC www.MicrosoftSharePointConference.com

  23. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related