CMS Migration Process

^_INVOLVES: Department & CMS Team 

• Meet the CMS Team & identify personnel to include in subsequent meetings
• Explain the migration process and set expectations of what is to come
• Explain what CMS is and how it differs from Dreamweaver 
• Show off sites and features available in the CMS
• Share the Content Analysis Form (which will assist with Meeting #2)

_INVOLVES:Department & CMS Team 

• Walk-through of existing site
• Talk through features, concerns, vision for site
• If there are special features, department explains the requirements
• CMS Team leaves meeting to analyze & identify solutions

_INVOLVES:
Department & CMS Team 

• Explain CMS so department can make informed decisions  
• Overview of Information Architecture needs
• Folder structure & names  
• Global elements & navigation  
• Permissions 
• Overview of Design options
  • Template options
  • Creative banner space
  • Photo needs
   
• Creation of a site map  

_INVOLVES:
Department & CMS Team 

• Receive decisions from department
• Discuss proposed solutions to special features; receive approval to proceed
• Create a timeline for training & migration
• Estimate hours it should take and propose a tentative deadline
• Plan a schedule of subsequent weekly/bi-weekly meetings 
• Sign-Off from department
  • Department understands the steps and agrees to the timeline 
   

_INVOLVES:
CMS Team 

• CMS Team prepares the CMS folder.
• CMS Team prepares and attaches the appropriate templates elements (global menu, identity, etc) to the folder.
• CMS Team builds user permissions.

_INVOLVES:
Department & CMS Trainer 

• Department personnel that will assist with migration of content to CMS receive training from the Web Specialist.
• Other department editors who will NOT assist with migration, but will maintain the site when it is complete will receive training AFTER the site has finished migrating.

_INVOLVES:
Department (with assistance from CMS Team as needed) 

• Cut and paste content
• Re-upload images and files
• Re-attach hyperlinks
• Re-build menu navigation
• Construct layout of the page

_INVOLVES:CMS Team 

• CMS Team develops and implement custom solutions for dynamic content and special features (as identified in the migration plan)  
• CMS Team demos the solution to the department.  
• Department identifies modifications needed and CMS Team makes the requested changes. 
•  ustom solutions are ready for use. 

_INVOLVES:
Department 

•  Department confirms that all content is migrated and present. 

_INVOLVES:
Department 

•  Department confirms that all hyperlinks work  
•  Hyperlinks should abide by the Best Practices. 

_INVOLVES:
Department 

• The department should test the site on as many browsers and computers as possible to ensure a consistent display. 

• Department confirms completion of site and readiness for Internet Presence Committee (IPC) review and go-live by completing the CMS Sign-Off Form.

_INVOLVES:
Department & Internet Presence Committee 

• Department attends an Internet Presence Committee (IPC) meeting to perform a walk-through of the new CMS site.
• Compliance with the web publishing best practices will address many of the common issues that surface during IPC review.
• IPC review typically results in:
  • Approval
  • Approval, pending minor corrections
  • Request for corrections and return for another review.
   

_INVOLVES:
CMS Team & Department 

• New CMS site launches occur on Monday mornings.
• Once approval is received by both the Department and Internet Presence Committee, the CMS team will determine the next available go-live date.
• Department confirms the date.

_INVOLVES:
Department 

• It is recommended that the department create a back up of their Osprey site offline.
• When the redirects are established, it will not be possible to view the old site from the web anymore. Should a department need to access old information that may have not been migrated, they will need to do so via offline, local copies of the site.

_INVOLVES:
CMS Team 

• CMS Team will prepare and implement the necessary technical redirects and aliases.
• CMS Team will update links to the site on the high-level UNF landing pages.
• When all technical steps are complete, the department will be notified so that they can check out their new site.

 _INVOLVES:
CMS Team 

• An announcement will be posted on the CMS login page.
• This message will inform other CMS editors to review their own sites and update any references to your site, now that the pages have moved and links have changed.

_INVOLVES:
Department & CMS Trainer 

• Once the site is live, any additional department editors who were not trained for and involved in the migration of content will receive CMS Training.