To enable migration of data to your System Center 2012 Configuration Manager environment, you must configure a supported Configuration Manager source hierarchy and one or more source sites in that hierarchy that contain data that you want to migrate.
 Note |
|---|
| Operations for migration are run at the top-level site in the destination hierarchy. If you configure migration when you use a Configuration Manager console that is connected to a primary child site, you must allow time for the configuration to replicate to the central administration site, to start, and to then replicate status back to the primary site to which you are connected. |
Use the information and procedures in the following sections to specify the source hierarchy and to add additional source sites. After you complete these procedures, you can create migration jobs and start to migrate data from the source hierarchy to the destination hierarchy.
Specify a Source Hierarchy for
Migration
To migrate data to your destination hierarchy, you must specify a supported source hierarchy that contains the data that you want to migrate. By default, the top-level site of that hierarchy becomes a source site of the source hierarchy. If you migrate from a Configuration Manager 2007 hierarchy, after data is gathered from the initial source site, you can then configure additional source sites for migration. If you migrate from a System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager hierarchy, you do not have to configure additional source sites to migrate data from the source hierarchy. This is because the these versions of Configuration Manager use a shared database which is available at the top-level site of the source hierarchy. The shared database contains all the information that you can migrate.
Use the following procedures to specify a source hierarchy for migration and to identify additional source sites in a Configuration Manager 2007 hierarchy.
Perform this procedure with a Configuration Manager console that is connected to the destination hierarchy.
To configure a source hierarchy
Identify Additional Source Sites of
the Source Hierarchy
When you configure a supported source hierarchy, the top-level site of that hierarchy is automatically configured as a source site, and data is automatically gathered from that site. The next action that you take depends on the version of Configuration Manager that is run by the source hierarchy:
- For a Configuration Manager 2007 source
hierarchy, after the data gathering finishes for the initial source
site, you can begin migration from only that initial source site,
or you can configure additional source sites from the source
hierarchy. You would configure additional source sites for a
Configuration Manager 2007 hierarchy to migrate data that is only
available from a child site. For example, you might configure
additional source sites to gather data about content you want to
migrate when that content was created at a child site in the source
hierarchy and is not available at the top site of the source
hierarchy.
- For a System Center 2012
Configuration Manager or System Center 2012 R2 Configuration
Manager source hierarchy, you do not need to configure additional
source sites. This is because these versions of Configuration
Manager use a shared database which is available at the top-level
site of the source hierarchy. The shared database contains all the
information that you can migrate from all of the sites in that
source hierarchy. This results in the data that you can migrate
being available from the top-level site of the source
hierarchy.
When you configure additional source sites for a Configuration Manager 2007 source hierarchy, you must configure the additional source sites from the top of the source hierarchy to the bottom. You must configure a parent site as a source site before you configure any of its child sites as source sites.
Use the following procedure to configure additional source sites for Configuration Manager 2007 source hierarchies.