Migrations Planning

A successful migration requires close coordination between members of the campus staff and Technology Services staff.  The Project Manager (PM) assigned to your project will be responsible for leading the project team. Campus leadership will attend a project kickoff meeting. The first task will be a campus meeting. At this meeting the campus administration and CIT will receive detailed information about the entire project. This includes a timeline with specific deadlines for the important milestones. 

The first piece of information due from the campus is the campus software list. The CIT facilitates and is responsible for the creation of a campus software list.  This list includes software purchased by central office departments, as well as any purchases made by the campus.  Technology Services will provide the CIT a spreadsheet with central office software purchases.  Accuracy in the campus software list is vital to a successful migration.  The project team will work closely with the CIT to assure accuracy of the campus software list.  The software list is used to develop the software images that will be installed during migration. There is a possibility that a particular software title on the campus software list may not be able to be installed due to incompatibility issues.

Depending on the size of the school and the number of computers and classrooms, the actual migration may take one to three weeks.  The PM will provide a day by day migration plan.  Each night a Technology Services crew will reimage the computers and install the software based on the campus software list.

A successful project requires good records, detailed testing, and good follow up on problems detected.  Your project team is committed to providing a quality project.  The software must be checked to ensure it works properly. The software quality check is a collaborative effort between Technology Services and the campus staff and takes several days to complete.  Any problems or concerns should be addressed to your PM and their team for resolution.

•  Migration Milestones per Campus
•  Software Licensing Compliance