Project Overview
Why are we migrating?
This is part of our ongoing commitment to delivering a secure, reliable and scalable service which supports future growth.
The good news is that this is largely a behind-the-scenes change, though customers can expect:
Improved long term performance and reliability, backed by Azure's world-class infrastructure
Enhanced security and compliance capabilities
Greater scalability as your needs grow
Faster future delivery of new features and enhancements
When does the migration start?
We have already commenced our internal preparations as part of our phased approach to the migration, firstly starting with our UAT environments.
Following completion of UAT testing and validation, we will confirm readiness for the production migration and provide a detailed timeline for the remainder of the year, including key dates, planned activities and any customer actions required in the coming weeks. We will ensure customers receive clear guidance and sufficient notice to prepare for the transition.
What is needed from me?
As part of the migration and testing programme, some customers may be asked to complete a small number of validation activities to help ensure services continue to operate as expected. The specific actions required will vary depending on your implementation and may include testing custom integrations, verify key business processes, or updating URLs where white-labelled solutions are in use. We will communicate any required actions in advance and provide detailed guidance and support throughout the process to help minimise disruption and ensure a seamless transition.
We recognise how important uninterrupted service is to our customers. To reduce any potential impact during the migration, we are scheduling the majority of the work outside normal business hours, including evenings and weekends. Our teams will be actively managing and monitoring the changes throughout the process, with safeguards in place to maintain service stability.
Our team is committed to keeping disruption to a minimum, to that end, we will be splitting the migration up into a series of phases to ensure relevant support and time can be dedicated to validating the changes, firstly starting with the User Acceptance Testing (UAT) environments.
The specific dates by Product for the UAT environment migrations and their testing window are as shown below:
UAT Environment | UAT Migration Date | Testing |
Marketplace Classic | 27th July (migrated - in testing) | Until 17th August |
Invoice Capture | 31st July (migrated - in testing) | Until 19th August |
Purchase-to-Pay (P2P) | 3rd August (migrated - in testing) | Until 27th August |
ProContract | 3rd August (migrated - in testing) | Until 1st September |
Sourcing | 3rd August (migrated - in testing) | Until 1st September |
Contract Management | 3rd August (migrated - in testing) | Until 1st September |
Supplier Relationship Management | 3rd August (migrated - in testing) | Until 1st September |
Following completion of UAT testing and validation, we will then commence preparations for production migration. The scheduled timeline for production migration is as follows:
Product Environment | Migration Dates |
Marketplace Classic | 28th - 31st August |
Purchase-to-Pay (P2P) | 28th - 31st August |
Invoice Capture Managed Service | 12th - 13th September |
Invoice Capture Hosted | 12th - 13th September |
ProContract | 9th - 11th October |
Sourcing | 9th - 11th October |
Contract Management | 9th - 11th October |
Supplier Relationship Management | 9th - 11th October |
We require users to be out of the associated system by 6pm on the Friday before the migration and kindly ask customers to make the necessary precautions to ensure this is possible ahead of the system being taken offline. A confirmation notification will be sent as soon as the migration is complete, planned to be the next working day post weekend outage, at which point we welcome you to resume usage of our solutions.
As part of the migration and testing programme, some customers may be asked to complete a small number of validation activities to help ensure services continue to operate as expected. The specific actions required will vary depending on your implementation and may include testing custom integrations, verify key business processes, or updating URLs where whitelisting is in use. We will communicate any required actions in advance and provide detailed guidance and support throughout the process to help minimise disruption and ensure a seamless transition.
For updates on the migration in real time, please visit the Proactis System Notifications & Monitoring page.
Cloud Migration FAQs
To help support our customers during this migration, we have produced a summary of Frequently Asked Questions as part of the upgrade. If you have a question not listed in this document, please reach out to your regular Proactis contact would will be happy to support.