Metalogix SharePoint Site Migration Manager 2010 - Frequently Asked Questions 

What are the limitations of the beta2 to RTM upgrade with SSMM2010?
SSMM 2010 supports all site and list types, master pages, page layouts, custom site columns,
managed metadata columns and content types. Support for Business Connectivity Services data
and workflows are not yet available.

Which specific releases are supported?
Beta2 build 4536 is supported. RC builds are not supported but are likely to work as expected.

Can I reorganize content or re-template sites when migrating from Beta2 to the RTM release?
Yes SSMM 2010 supports both re-templating and content re-organization.

Is this a supported migration / upgrade path?
Yes, SSMM 2010 uses the SharePoint object model to migrate data to the RTM instance
and is therefore a fully supported scenario.

Our Beta2 instance is now offline. Can we migrate data from a backup or offline database?
Yes, offline content databases are supported.

How is the Beta2-to-RTM migration path priced?
Please contact sales@metalogix.net for pricing information.

We currently have content in both SharePoint 2010 Beta 2 and MOSS 2007.
Are both of these content sources supported?
Yes. SharePoint Portal Server 2003, WSSv2, MOSS 2007, WSSv3, SharePoint Foundation Beta2
and SharePoint Server 2010 Beta2 are all supported sources.

In addition to Beta2 do you support any other migration scenarios?
Yes. Metalogix also supports migration from Exchange Public Folders, MCMS2002, NTFS FileShares,
EMC/Documentum eRoom, Oracle Content Server (Stellent), Blogs (Blogger, WordPress, Telligent) and many others.

We have a large amount of both test data and real content in our Beta2 instance.
Is it possible to migrate a subset of the data from the Beta2 instance to the RTM release?
Yes. With SSMM2010 you can granularly select items, folders, lists or sites with rich filter support and
migrate only the subset of content you specify from the Beta2 instance to your SharePoint 2010 RTM server.

We have implemented customer features and webparts in our Beta2 instance. Can these be migrated?
Custom webparts and features need to be deployed to the target server using standard deployment processes.