Determine Whether to Migrate Configuration Manager 2007 to Configuration Manager 2012

Updated: May 1, 2011

Applies To: System Center Configuration Manager 2012

In Microsoft System Center Configuration Manager 2012, the built-in migration functionality replaces in-place upgrades of existing Configuration Manager infrastructure by providing a process that transfers data from active Configuration Manager 2007 sites. The functionality provided by migration helps you maintain investments that you have made in configurations and deployments while you can take full advantage of core changes in the product introduced in Configuration Manager 2012. These changes include a simplified Configuration Manager hierarchy that uses fewer sites and resources, and the improved processing by use of native 64-bit code that runs on 64-bit hardware.

Migration can transfer most data from Configuration Manager 2007. If you do not migrate Configuration Manager 2007 to Configuration Manager 2012, or if you migrate data and want to maintain objects that migration does not migrate, you must re-create non-migrated objects in the new Configuration Manager 2012 hierarchy.

Use the following sections to help you plan for data you can or cannot migrate to Configuration Manager 2012:

Data That You Can Migrate to Configuration Manager 2012

Migration can migrate most objects from Configuration Manager 2007 to Configuration Manager 2012. The migrated instances of some objects must be modified to conform to the Configuration Manager 2012 schema and object format. These modifications do not affect the data in the Configuration Manager 2007 database.

You can migrate the following types of objects:

  • Collections

  • Advertisements

  • Boundaries

  • Software distribution packages

  • Virtual application packages

  • Software Updates:

    • Deployments

    • Deployment packages

    • Templates

    • Software update lists

  • Operating System Deployment:

    • Boot images

    • Driver packages

    • Drivers

    • Images

    • Packages

    • Task sequences

  • Desired Configuration Management:

    • Configuration baselines

    • Configuration items

  • Asset Intelligence customizations

  • Software metering rules

Data That You Cannot Migrate to Configuration Manager 2012

Migration cannot successfully convert some Configuration Manager 2007 objects and data to the Configuration Manager 2012 database schema during migration. These objects and data must be recreated in the Configuration Manager 2012 database.

You cannot migrate the following types of objects:

  • Queries

  • Security rights and instances for the site and objects

  • Configuration Manager 2007 reports from SQL Server Reporting Services

  • Configuration Manager 2007 web reports

  • Client inventory and history data

  • AMT client provisioning information

  • Files in the client cache

See Also