We use cookies to ensure that we give you the best experience on our website. You can change your cookie settings at any time. Otherwise, we'll assume you're OK to continue.

Internal Communications
  • Need to know

    Need to know
  • Latest news

    Latest news
  • Events and Activities

    Events and Activities
  • Lectures and Seminars

    Lectures and Seminars

Migrating (moving) University IT services into their new home

(10 March 2017)

In last week's Signposts we introduced the NWP Core project and explained about the new data centres. Now they're in place, we're preparing to move or migrate University IT services into them, and this week we're explaining what migrations mean (and look like) to you.

So the University can benefit from the security, resilience and increased confidence in IT service availability that the new data centres bring, we need to start using them. That begins when we move University IT services from their current home into these new locations. The process of moving or relocating these IT services is referred to as migration.

When a service is migrated into its new home we back-up and create a copy of the service, move the copy into the new data centre and then carry out basic testing to confirm its availability and basic functioning.

We've done a handy infographic to illustrate this process - you can see it here:

  • In order to limit the impacts on the operational activities of the University, we will be migrating services during the evening and early hours of the morning.
  • When we do this, the service or services being migrated will be unavailable to users from 11pm (23:00 BST) the night prior to the move. 
  • We will aim to have the migrated service available for use for 9am (09:00 BST).

About testing

Once a service has been migrated, CIS will carry out basic testing to ensure it is available however there will be a number of services where CIS will not be in a position to carry out user specific tests (i.e. those to check that key functionality, processes, links to other interconnected systems, etc. work as expected).

Departments who use IT for specific processes should identify a series of key task to check, once the service is restored. These will depend on the system and the function of the department but should be general tasks which you do daily. The aim is to run through them to check that the service performs in exactly the same way it did pre-migration (i.e. ‘yesterday’).

Next week, we'll be telling you about the ways in which we'll be sharing information about the Core project once the migrations start. Check back next week so you'll know where to find out when the services you use are going to be migrated.

Full details about this project can be found at:

Have something to include?

Please liaise with the designated contact for your department or college. For further guidance, email

Get in touch