As we said when we shared the delviery timeline- while we’re on track now, in big programmes like this, things can go wrong. So,we’re going to thoroughly assess where we are during August, to confirm that we’re still on track. If not, we’ll tell you, so that you’ve got plenty of notice 

We've already completed a Proof of Concept for our data migration approach and will now be preparing to action multiple dry-runs of data migration between now and the end of September, including after that a final dress-rehearsal. 

This ensures that we both validate the data is migrating correctly, and practice our process for moving the data efficiently at Go-Live 

We're also actioning a parallel-run – which means that behind the scenes we are ingesting data from your current inputs to Solera and ensuring that we are processing those inputs in the same way. 

Either during the cutover period, or a short window after Go-Live, our rollback plan would be to switch back to Solera.  

This would mean that Portal users would log in to Solera if the rollback happened, and API would have to repoint their integration to Solera (if they’ve already switched) to continue operations. 

We have already started to define our user migration rules to show how we will migrate existing users into Navigate, this includes our approach to how administrators will be set up.  

You may have seen on the Timeline a 3-month period from July to September where we will share with you several times how your users would land IF we applied these rules and migrated at that point. 

This gives you chance to cleanse and make changes in Solera where users are not where you are expecting them. We'll also refine the user migration rules if some users are moving over unexpectedly. 

Then we will support org admins to make changes/updates for Users in Navigate or add new users then in the 3 weeks of November between the User migration and the Go-Live on 24 November.