Download white paper that compares the features of Metalogix SharePoint Migration Manager to SharePoint's standard on-board tools.
Metalogix Site Migration Manager offers the following significant advantages when compared to "In-Place" or "Database Attach" upgrades:
A key feature of Metalogix is the ability to delegate the migration process to content owners, giving them the flexibility to choose when and how content gets migrated. Because Metalogix uses the standard SharePoint API to move content from one location to another, the user simply needs to have rights to the content to move it. In many organizations, the content owners may have unique schedules or may want to be in control of the process. This process provides that flexibility and lets them fit content migration into their own schedules. IT empowers key content owners or power users to facilitate the migration based on business requirements. A distributed approach also has the benefit of reducing the workload for IT staff, and helps to ensure buy-in from content owners on the new SharePoint 2010 system.
One highly useful feature in Metalogix is its ability to perform granular migrations of content. Content owners can decide which portions of a site collection get migrated first, and then migrate the content in waves, rather than en masse. These capabilities allow organizations to perform phased pilots or Proof of Concept migrations, which reduce the risk associated with the project.
Site structure can be redefined while migrating, sites and site collections can be split into multiple targets, sites can be re-templated, and administrators and content owners can define what content is migrated. You can make visual and navigational changes to the content, so a site architect can reorganize and restructure the content and implement the enterprise taxonomy more easily.
Because Metalogix can pull and push data from multiple sources and targets, it allows organizations to collapse multiple SharePoint 2003 or 2007 farms into a single SharePoint 2010 farm. Organizations are often surprised to discover how many instances of SharePoint exist across multiple departments. Often, individual team sites were created on desktops and rogue servers, while content was decentralized across the organization. This content can be brought back under centralized control using Metalogix, and multiple SharePoint sites and any 2.0 or 3.0 version can be consolidated onto a single managed farm. In addition, consistency of look and feel can be enforced across the migrated content with Metalogix’s ability to re-template the content. Finally, because a new SharePoint 2010 farm is created for the migration, new hardware, software versions, 64-bit architecture, and newer database servers can be provisioned, all with best-practice architecture and without designing around the flaws of the previous SharePoint version.
Server virtualization is a hot topic in today’s business data centers. Many organizations are opting to virtualize the majority of their server infrastructure, including SharePoint servers. The fact that Metalogix is target-agnostic gives you the flexibility to build the new SharePoint 2010 farm on virtual machines if required. This applies to virtualization software from any one of the common virtualization platforms in use today.
Access to the Metalogix client allows SharePoint content owners to easily reorganize the SharePoint server if structural mistakes are made. Instead of living with an inefficient structure, they can be rectified quickly. The following list details several of the more popular management features in Metalogix: list splitting, list merging, rename and reorganize sites, lists and libraries, reorganize folder content, split sites across multiple content databases, merge sites into a single site collection, compare sites, lists and libraries.
Metalogix provides native capabilities to migrate directly from backup files to live sites, eliminating the need to build temporary farms and attach live databases for a migration. Simply point to an offline database or even a backup file to extract the data directly and merge it into a live SharePoint 2010 environment. This accommodates scenarios such as secured environments where source and destination server are isolated from each other.