As you transition your websites from SharePoint 2010 to Sitefinity, you will follow a series of steps called the CMS transition process. You and your team will participate in a series of planning and working meetings to identify resources, determine site features and functionality, create content, build your pages and launch your site. While you’re considered a “client” of the CMS Transition Team, you’re also responsible for much for the work and planning involved in the transition process.

Teams involved

CMS transition team

The CMS transition team is made up of staff from CU Anschutz Communications, CU Denver University Communications (UComm) and the Office of Information Technology (OIT). These web professionals will guide you through the CMS transition process

  • Delivery Manager – facilitates transition process, client's primary point of contact
  • Information Architect/User Experience expert – provides sitemap, homepage wireframe, business analysis
  • User Interface Designer – consults on homepage design, best practices for displaying content
  • Application Manager – manages new feature development
  • Content Advisor – provides web writing training, content advising and content review
  • CMS Trainer and Content Developer: provides GatherContent overview, Sitefinity 101 training, Open Labs


Client team

Members from your school/college/campus unit who will be most involved in the transition and creation of your new website. Some or all of the following roles may overlap depending on the size of your campus unit and what resources you have available (many smaller departments just have one representative working on their website transition). 

  • Project sponsor
  • Project lead
  • Web content writer
  • Website owner/builder
  • School/college/unit communicator

Transition phases

The CMS transition process consists of five phases. The length of the process can vary greatly, depending on the size of your site, new development requirements, resource availability and the pace at which the deliverables are met in each phase. The CMS transition team leads the client team through the five phases. To date, the longest part of the process is creating/finalizing content and building out the new site in Sitefinity.

Phase 1: Kickoff

When it's time to begin your transition to Sitefinity, you will receive an engagement package with information on the process, analytics of your current SharePoint site and instructions on how to get started. Your unit's CMS transition kickoff meeting will be scheduled shortly after.

  • Transition overview
  • Review of strategic web priorities
  • Elements of user experience
  • Discuss schedule and resources

Phase 2: Discovery

Between the kickoff meeting and the discovery workshop, your team will identify website goals, audiences and feature requests for your new Sitefinity website. To gather additional stakeholder feedback, we also encourage groups to survey their community at this time. 

  • Client team presents:
    • Site goals
    • Audiences
    • Feature/functionality requests
  • Discuss sitemap, development process and content considerations

Phase 3: Build prep

During the build prep phase, your team will have a working meeting with the IA/UX expert to review a proposed sitemap and homepage wireframe. At this time, the development team will be planning for new features and timelines for releases.

The Build Prep Meeting is the last step of this phase and the following will be discussed:

  • Review finalized site elements: sitemap, homepage wireframe, solutions to feature requests
  • The transition team will review:
    • Training and permissions
    • @Web Resource Site
    • Features development process
    • How to report bugs and make additional feature requests
    • GatherContent online collaboration tool

Phase 4: Build

Before you start building your site, you will attend Sitefinity 101 training, at which time you will be granted permissions to Sitefinity. Content creation and building out your site will be the longest part of the process. Many units consider hiring a content writer or site builder to assist with this work. 

  • Homepage design meeting with UI expert
  • Requirements gathering and design reviews of new features
  • Feature development
  • Check-ins with delivery manager


Phase 5: Launch

  • Launch date identified
  • Stakeholder sign off
  • Transition team site review (performance, accessibility, branding)
  • Launch process:
    • Change Advisory Board (CAB) submission for site launch (completed by transition team)
    • Go/no-go meeting
    • Deploy website to production
    • Configure site redirects
    • Search indexing
    • Clear Google cache
    • Retire SharePoint site
    • Client QA (quality assurance)


Express site transitions

In order to expedite the CMS transition project, a number of sites have been identified to move to Sitefinity via an "express" process. There are 17 sites that have chosen to be moved to Sitefinity via the express process based on the size of the site and the traffic to the current SharePoint site. These sites will be transitioned to Sitefinity as-is and then re-worked once in the new CMS.

If your campus unit's website has been chosen to be moved as an express site, you will be contacted by the project lead, Chloe Rankin based on the transition schedule.