SCCM migration does not have to be painful. In fact, most packages, operating system images, and task sequences can be quickly migrated across SCCM servers or to a new site.
Here is the most important step of the package migration: You must specify a UNC path on the NEW SCCM server. In this example, I am using e:\PEI-Sources directory. In this example E:\ is my SCCM content drive on the new server.
The next step is importing the package from new SCCM server.
During import, the information you entered for target export directory IS updated in each imported package. This means there is no reason to alter paths in your programs as it is taken care of “auto-magically”. The screenshot below shows what happens if you chose to export to an incorrect location – new SCCM package is now referencing the directory you exported to.
After the package import is complete, do not forget to distribute content.
This is an error you will receive if the distribution manager fails to locate the source path.
If the package distributes correctly, your data is migrated and ready for deployment from the new server.