Skip to main content

Part of Migration and implementation

Kick off

How to kick off your migration effectively, with everyone who will be involved in the process. 

Kick off

A kick off meeting is for everyone who will be involved in the migration. They discuss the end to end process of migrating between systems. The goal is to assign roles and ensure everyone knows what needs to happen and when. 

Some activities happen during the kick off meeting itself. Others happen outside the meeting, as you go through the migration.

It may be useful to setup a shared area where project information, plans and documents can be shared. You can use tools such as SharePoint or Teams to share information.  


Who is involved

The people, teams or organisations who might be required in this stage of the migration are:

  • project manager 
  • practice manager 
  • practice staff 
  • lead GP 
  • new GP clinical system supplier 
  • integrated care board (ICB) 
  • IT delivery partner
  • representatives from other care settings such as:
    • community
    • hospice
    • multi disciplinary team (MDT) leads 

The practice may also choose to inform the care quality commission (CQC) of the change of GP clinical system. This will avoid unplanned visits that might coincide with the migration. 


Kick off tasks

Checklist:
  • agree key milestones, dates and activities
  • define how to manage the migration
  • identify key stakeholders
  • plan for your clinical risk assessment

Downloadable checklists

To help you organise this stage of the migration we have developed the following digital and printable checklists:


Agree key milestones, dates and activities

By now you will have agreed a provisional go live date. You should also have received a schedule of key migration dates from the new supplier.  

You will need to produce a schedule of provisional dates for each milestone. Consider the activities and people involved to ensure their success. 

The key milestones are: 

  • technical survey 
  • initial data production and testing days 
  • final data production and cutover 
  • go live 
  • training days

Once you have a provisional plan in place, confirm all the dates with the new supplier.

When developing your plan, you should: 

  • hold weekly migration meetings 
  • block time in people’s diaries 
  • plan around holidays and training 
  • plan around busier times 
  • book rooms for training and other migration activities 
  • reduce bookable rota slots during cutover, so there is less data to re-enter into the live system
  • reduce bookable rota slots post go live, to allow time to adjust
  • assess how the migration may affect QOF reporting and plan accordingly

Define how the migration will be managed

You will need to manage the migration project effectively to meet timelines.

Create a central list of actions for each phase showing:

  • a provisional date for each action
  • who will complete them 
  • the current status

Decide who takes responsibility for managing risks. Decide on strategies to deal with risk.

Establish a process for maintaining a hazard log.

Identify scenarios that might mean you have to rollback changes and create a plan for how to do this. 

Detail any system downtime and impact on core hours.

Recommendation

Use a spreadsheet that everyone can access. The project manager should manage it. 


Identify key stakeholders

Identify who will be involved in the migration, their roles and responsibilities. 

Within your practice common roles are:

  • practice manager
  • practice staff
  • general practitioner to act as lead GP
  • clinical staff, including remote workers

You will need to involve roles, teams and organisations from outside your practice.

As set out in the GP IT Operating Model the ICB must ensure the following services and resources are available to the practice to support the implementation:

  • project management including supplier management
  • local training to supplement supplier provided training at go live and post go live
  • registration authority service (RA) for smartcard and access controls
  • clinical safety assurance
  • information governance (as needed)
  • technical IT services
  • additional IT infrastructure where essential to project
  • updating and upgrading of any ICB provided digital systems which integrate with the GP clinical system
  • funding for data migration (data extracts and imports) 

Surrounding and community services should also be contacted. Examples include:

  • pharmacies
  • pathology laboratories
  • out of hours
  • 111
  • any screening services 

You will also need to work with the current and new suppliers of the GP clinical system.

Remember to involve third party system suppliers that integrate with your current system. Examples include:

  • DocMan
  • Apollo Scan
  • DispensIT  
  • GP telephony

Please note

If people are not present in any meetings, think about how you will keep them up to date. It is important that they understand their roles. 


Plan for your clinical risk assessment

When everyone has agreed the data migration plan, complete a clinical risk assessment. An initial clinical risk assessment may have been required as part of the earlier choice process. This will now need to be reviewed and finalised.

Consider any risks to clinical and patient safety. Clinical safety is the responsibility of the practice but they can request specialist support from the ICB.

If there is a risk from migrating, you should escalate it to the relevant management. 


Last edited: 27 October 2026 9:28 am