The following table identifies the type of objects that you can migrate with each job type.

Object type	Collection migration	Object migration or objects modified after migration
Advertisements	Yes	No
Boundaries	No	Yes
Software distribution packages	Yes	Yes
Virtual application packages	Yes	Yes Important While you can migrate virtual application packages by using object migration, they cannot be migrated by using the migration job type of Previously Migrated Object Migration. Instead, you must delete the migrated virtual application package from Configuration Manager 2012 and then create a new migration job to migrate the virtual application.
Software update deployments	Yes	No
Software update deployment packages	Yes	Yes
Software update deployment templates	No	Yes
Software update lists	No	Yes
Operating system deployment boot images	Yes	Yes
Operating system deployment driver packages	Yes	Yes
Operating system deployment drivers	Yes	Yes
Operating system deployment images	Yes	Yes
Operating system deployment packages	Yes	Yes
Task sequences	Yes	Yes
Configuration baselines	Yes	Yes
Configuration items	Yes	Yes
Asset Intelligence catalog	No	Yes
Asset Intelligence hardware requirements	No	Yes
Asset Intelligence software list	No	Yes
Software metering rules	No	Yes

When you create a collection migration job, you must select one or more collections, and then you see all the objects that are associated with the selected collections. By default, all objects associated with the selected collections are selected for migration, but you can clear the objects that you do not want to migrate with that job. When you clear an object that has dependent objects, those dependent objects are also cleared, and then added to an exclusion list. This action removes them from automatic selection for future migration jobs. You must manually edit the exclusion list to remove objects that you want to be automatically selected by future migration jobs.

When you migrate content for deployments, you must assign the content object to a site. This site then becomes the owner for that content. Although the top-level site of your Configuration Manager 2012 hierarchy migrates the metadata for content, it is the assigned site that accesses the original source files for the content across the network.

To minimize the network bandwidth that is used during migration, consider transferring ownership of content to the closest available site. Because information about the content is shared globally in Configuration Manager 2012, it will be available at every site.

Consider relocating the source files in the Configuration Manager 2007 hierarchy before you start migration or relocate them to the central administration site during migration. This action might avoid a Configuration Manager 2012 site accessing the source files across a low bandwidth network connection. Even though information about content is shared to all sites by using database replication, any content that you assign to a Configuration Manager 2012 primary site and then deploy to distribution points at other primary sites, transfers by using file-based replication. This transfer is routed through the central administration site and then to the additional primary site. By centralizing packages that you plan to distribute to multiple primary sites before or during migration when you assign a site as the content owner, you can reduce data transfers across low bandwidth networks.

When you migrate data to Configuration Manager 2012, you must assign one or more role-based administration security scopes to the set of objects in the migration job. This ensures that only the appropriate administrative users have access to manage this data after migration. The security scopes that you specify are applied to each object in the migration job. If you require different security scopes to be applied to different sets of objects, and you want to assign those scopes during migration, you must migrate the different objects in different migration jobs.

Review how role-based administration works in Configuration Manager 2012, and if necessary, configure one or more security scopes for the data that you migrate to control who will have access to the migrated objects in Configuration Manager 2012, before you configure a migration job.

For more information about security scopes and role-based administration, see .

When you configure a migration job, you see a list of actions that you must take to ensure a successful migration and a list of actions that Configuration Manager takes during the migration of the selected data. Review this information carefully to verify the expected outcome.

By default, a migration job runs immediately after it is configured, unless you change the schedule of a migration job before it begins processing.

By default, migration jobs do not overwrite data in the Configuration Manager 2012 database, unless you configure the migration job to skip or overwrite data that has previously been migrated to the Configuration Manager 2012 database.

You can exclude specific objects from a collection migration job. When you exclude a specific object from a collection migration job, that object is added to an exclusion list. The exclusion list is a global list and contains all objects that you have excluded from migration jobs created for any source site in the active source hierarchy. Objects on the exclusion list are still available for migration in future jobs but are not automatically selected as an included object when you create a new collection-based migration job.

You can edit the exclusion list to remove objects that you have previously excluded. After you remove an object from the exclusion list, it is then automatically selected when an associated collection is specified during the creation of a new migration job.

Configuration Manager 2012 can migrate any of the default user collections, device collections, and most custom collections from the source hierarchy. However, collections that contain both users and devices make up the exception. Configuration Manager 2012 cannot migrate these collections.

The following cannot be migrated:

• A collection that contains both users and devices.
  
  
• A collection that contains a reference to a collection of a different resource type. For example, a device-based collection that has either a subcollection or a link to a user-based collection.
  
  

An empty collection is a collection that has no objects associated with it. When Configuration Manager 2012 migrates an empty collection, it converts the collection to an organizational folder that contains no users or devices. This folder is created with the name of the empty collection under the User Collections or Device Collections node in Configuration Manager 2012.

When you migrate collections that are linked to other collections or that have subcollections, Configuration Manager 2012 creates a folder under the User Collections or Device Collections node in addition to the linked collections and subcollections.

When you specify a collection to migrate in the Create Migration Job Wizard, any dependent collections are automatically selected to be included with the job. This behavior ensures that all necessary resources are available after migration.

For example: You select a collection for devices that run Windows 7 and that is named Win_7. This collection is limited to a collection that contains all your client operating systems and that is named All_Clients. The collection All_Clients will be automatically selected for migration.

Because Configuration Manager 2012 collections are global data and are evaluated at each site in the hierarchy, plan how to limit the scope of a collection after it is migrated. During migration, you can identify a Configuration Manager 2012 collection to limit the scope of the collection that you are migrating so that the migrated collection does not include unanticipated members.

For example, in Configuration Manager 2007 collections are evaluated at the site that creates them, and at child sites. An advertisement might be deployed to only a child site, and this would limit the scope for that advertisement to that child site. In comparison, Configuration Manager 2012 evaluates collections at every site, and associated advertisements would then be evaluated for each site. Collection limiting lets you refine the collection members based on another collection to avoid the addition of unexpected collection members.

When you migrate a collection that contains criteria that identifies a Configuration Manager 2007 site, you must specify a specific Configuration Manager 2012 site. This ensures that the migrated collection remains functional in your Configuration Manager 2012 environment and does not increase in scope.

By default, collection-based migration jobs disable advertisements that migrate to Configuration Manager 2012 and any programs that are associated with the advertisement. When you create a collection-based migration job that contains advertisements, you see the option Enable advertisements after they are migrated to Configuration Manager 2012 on the Settings page of the Create Migration Job Wizard. If you select this option, programs that are associated with the advertisements are enabled after they have migrated. As a best practice, do not select this option and instead, enable the programs after they have migrated when you can verify the clients that will receive them.

Note
You see the Enable advertisements after they are migrated to Configuration Manager 2012 option only when you create a collection-based migration job, and the migration job contains advertisements.

To enable a program after migration, clear the option Disable this program on computers where it is advertised on the Advanced tab of the program properties.