You can complete the Configuration Manager 2012 migration process when you no longer want to migrate data from Microsoft System Center Configuration Manager 2007. Before you complete migration, make sure that you have successfully migrated all the objects, collections, and clients that you need.
After you complete migration from a Configuration Manager 2007 hierarchy, and this hierarchy no longer contains resources that you manage, you can decommission the Configuration Manager 2007 sites and remove the related infrastructure from your environment.
Use the following sections to help you plan to complete migration from a Configuration Manager 2007 hierarchy:
Plan to Stop Gathering Data
Before you complete migration and clean up migration data, you must stop gathering data from each source site in the active source hierarchy. To stop gathering data from each source site, you must perform the Stop Gathering Data command on the bottom tier source sites, and then repeat the process at each parent site. The top-level site must be the last site on which you stop gathering data. You must stop data gathering at each child site before performing this command on a parent site.
When you stop gathering data from a source site, shared distribution points from that site are no longer available as content locations for Configuration Manager 2012 clients. Ensure that any migrated content that the Configuration Manager 2012 clients require remains available by using one of the following options:
- Distribute the content to
Configuration Manager 2012 distribution points.
- Upgrade shared Configuration Manager 2007
distribution points to Configuration Manager 2012
distribution points.
After you stop gathering data from each source site in the active source hierarchy, you can clean up migration data. Until you clean up migration data, each migration job that has run or that is scheduled to run remains accessible in the Configuration Manager console.
For more information about source sites and data gathering, see Planning for Source Hierarchies in Configuration Manager 2012.
Plan to Clean Up Migration Data
The last step to complete migration is to clean up migration data. You can use the Clean Up Migration Data command after you have stopped gathering data for each source site. This action removes data about the active source hierarchy from the Configuration Manager 2012 database. It is optional.
When you clean up migration data, most data about the migration is removed from the Configuration Manager 2012 database. However, details about migrated objects are retained. With these details, you can use the Migration workspace to configure the same Configuration Manager 2007 hierarchy as the active source hierarchy to either resume migration, or to review the objects that you migrated and site ownership of objects.