What Doesn’t Migrate with SharePoint Built in Import/Export and other known issues

​Item created by, created date, last modified date
Workflows (Definitions)
Workflow State & Tasks
Workflow History
Check in/check out state
Audit logs
Usage Logs that have not been processed
List configuration/app configuration
Site collection settings (Site Collection Ownership, Quota, email notification settings and a lot more)
Personalized views
Alerts
Recycle bin state/items including admin and user Recycle bin items
Lookup lists have issues due to remapping of object GUIDs
Object GUIDS are not preserved (This causes all sorts of weird things and can cause issues down the road. Empty folders may not migrate) This includes using import/export in STSADM or Windows Powershell, SOAP or Web services as well both result in loss of object id consistency including reparenting. The only way to avoid this is using the Content Migration object model.
Empty objects may not migrate (Discussion lists may have some problems related to this, and some folder structures may be remapped.)
Users that no longer exist are removed during import/export (related to ownership being re-written)
Surveys that are not completed will not be exported
Global Navigation inheritance issues (parenting challenges)
Known issues with conflicts when used with content deployment
No migration of features, solutions or assemblies associated with site/web (Must be manually migrated if separate farm and exist on destination)
Content overwritten if exists
Site dependencies on Site Collection Gallery lists (example if you migrate a web the parent site collection may have galleries that the web uses i.e. galleries include some look and feel, masterpages, images, features, and webparts.) known to have issues (Need more detail)
No list level migration (granularity is site level in 2007; Windows Powershell SharePoint Cmdlet in 2010 gives you list level) Thanks @toddklindt
Scale limitations (reliability goes down the larger the site <25gb add="" as="" best="" br="" case="" compression="" database="" databases="" dedicated="" exports="" fidelity="" higher="" if="" increases="" is="" it="" large="" likelihood="" migration="" no="" note:="" parameter="" that="" the="" will="" work.="" you=""> Portal Template Global Nav known to have issues (Need detail. Problem appears to be associated with site collection property loss)
Security remapping AD group challenges for groups between 2 untrusted forests
Versions of aspx pages (Need more detail)
Can’t change site template during migration
Can’t consolidate sites during migration
No good list of what fails to import
blocked file types
files over max file size
Objects that don’t contain objects may not be migrated (See comments in Gary LaPointe’s Export lists blog)
Post migration sync (No way to migrate again. If template already chosen or not blank)
No support between farms of different builds and versions. Have to be exact same version number (This may be different in 2010).
No ability to target a specific content without manual intervention (limiting all others or setting capacity high)
You can experience problems if you re-run Stsadm on site content that has already been imported. If that occurs, all list items that are not document libraries are duplicated on the target site.​

If you have any questions you can reach out our SharePoint Consulting team here.