Configuration Manager 2007 to 2012 Migration


In this post, I'm going to do a walk-through of setting up a migration from Configuration Manager 2007 to Configuration Manager 2012 and the process to migrate a package.

Lab Environment

CM07.CONTOSO.LOCAL = My Configuration Manager 2007 Site Server and database

CM12.CONTOSO.LOCAL = My Configuration Manager 2012 Site Server and database

I will be using the computer account of my Configuration Manager 2012 site server for the migration account. You could use a regular domain account but best practice is to delegate the computer account of the CM12 site server for the migration.

Things to know before starting:

Source Site Account: This account is used to access the SMS Provider of the source site.

  • For a Configuration Manager 2007 SP2 source site, this account requires Read permission to all source site objects.
  • For a System Center 2012 Configuration Manager source site, this account requires Read permission to all source site objects.

Source Site Database Account: This account is used to access the SQL Server database of the source site and requires Read and Execute permissions to the source site database.

When gathering data, the following network protocols and ports are used:

  • NetBIOS/SMB – 445 (TCP)
  • RPC (WMI) - 135 (TCP)
  • SQL Server - 1433 (TCP)

Verity these ports are opened for the SQL server the CM07 site is running on.

Performing the Migration:

The first thing I'm going to do is delegate the computer account of CM12.CONTOSO.LOCAL read permissions to the CM07 site this will be used for the "Source Site Account" . You can use any domain account as the "Source Site Account", but it is considered best practice for security to use the computer account of the CM12 site server.

In the CM07 console, navigate to Site Database > Security Rights > Users > Right Click Manage ConfigMgr Users and follow the wizard.

In the user name, add the computer account of the CM12 site server:


Next we need to give the CM12 site server computer account the required permissions to migrate data.

I will give the computer account read permissions to the CM07 site (NOTE: If you plan to perform DP Sharing / Upgrade you should add modify & delete).


I Also gave the computer account Read permission to Packages (NOTE: This account will need read permission for each object type you want to migrate. For example: Collection, Operating System Images etc. In my case I'm only going to migrate Packages so read rights on packages will work for this migration).


Next thing we need to do is give the CM12 computer account a login into the CM07 database using SQL Management Studio.


Now we will set the required permissions for the new login account


The above steps will give the computer account to minimum permissions to migrate data from our CM07 to our CM12 site.

Now we will need to setup the migration in out CM12 configuration manage console:


Everything should go through just fine.... Hopefully :)


Now that you have successfully gathered data from our CM07 heirachy you will need to create a migration job (This is what actually will bring objects from the CM07 site to the CM12 Site). I will show how to create a migration job that will migrate a package.


Choose the package(s) and other objects you want to migrate. You can also migrate package(s) using the collection migration and have the option to migration collections and advertisements related to the package but in this case I only wanted to migrate the package.


Click next on the Assign ownership (If using a CAS you could select the site you want to assign ownership to)

If you have custom security scopes you can assign it in the Security Scope wizard (or create one) in my case I choose the default:


In the settings, you can select when you want the migration to run. In my case, I left the default to run now.


Completion Wizard should appear!

Verify the job actually ran successfully


Your migrated objects will show up in your CM12 site:



Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of any included script samples are subject to the terms specified in the Terms of Use