Migration plan from 12.x to 13.0

Timelines and steps

S.No	Description	Responsibility	Down time required?	Efforts	Comments
1	New Linux machine provisioning. (Red Hat 8,9, Centos 7, 8, Debian 9,10,11) If Windows authentication is intended then the PCS machine should be on the same domain as SQL Server.	Customer	No	-
2	Deployment of PCS 13.0	Expertflow	No	1 day	Access to new Linux machine must be provided
3	PCS VXML Application deployment	Expertflow	No	4 hours	Access to CVP must be provided
4	Configuration and testing of PCS 13.0 with a test IVR	Expertflow/Customer	No	1 day	Access to Linux machine and CVP must be provided. A test agent and a test DN should be created
5	PCS reports configuration on CUIC	Expertfow	No	5 hours	CUIC should be accessible
6	Partial data migration from 12.x database to new database and divert live IVR application to new PCS APIs Services, Agents, Questions, Surveys data will be migrated to new database to have same surveys in new PCS Update the live VXML application to interact with the new PCS APIs	Expertflow	Yes	5 hours
7	Migrate the survey_feedback tables content to new PCS database	Expertflow	No	8 hours

The PCS 13.x version is a significant upgrade, built from the ground up while retaining the existing database schema. This version streamlines the system by removing unnecessary tables and fields. Though the IVR API request and response payloads remain consistent, the endpoints have been updated. Follow the steps below to upgrade to PCS 13.x.

Create a New Database for PCS

1. Backup Existing Database: Before making any changes, ensure you back up your current database to avoid any data loss.

2. Set Up a New Database:

   • Create a new, empty database instance for PCS 13.x.

   • Configure the database with the necessary user permissions and roles to match the requirements of PCS 13.x.

3. Verify Connection:

   • Ensure that the new database is accessible from the server where PCS will be deployed.

   • Test the connection to confirm that there are no connectivity issues.

Deploy PCS 13.0

1. Follow the Deployment Guide: Use the provided PCS 13.0 deployment guide to install the application.

   • Prerequisites: Ensure all system requirements are met.

   • Configuration: During the installation process, point PCS 13.0 to the newly created database.

   • Verification: After deployment, verify that the application is running and can connect to the new database.

2. Initial Setup:

   • Log in to the PCS 13.0 application.

   • Complete any initial setup required, such as configuring admin users and basic settings.

Configure and Create a Test Survey

1. Perform Initial Configuration:

   • Navigate to the configuration settings within PCS 13.0.

   • Update settings such as notification rules, Cisco type, question weights, and any other required configurations.

2. Create a Test Survey:

   • Use the PCS 13.0 interface to create a sample survey.

   • Ensure all components, such as questions and prompts, function as expected.

3. Test Survey:

   • Deploy the test survey to verify the end-to-end workflow.

   • Ensure that the IVR API endpoints respond correctly and that survey responses are recorded in the new database.

Migrate Data from the Existing Database to the New Database

1. Plan the Migration:

   • Identify the data that needs to be migrated from the old database to the new one. (service, agent, question, survey, survey_feedback)

   • Review the schema changes in PCS 13.x to understand which tables and fields are no longer needed.

2. Extract Data:

   • Export the service, agent, question, survey_feedback data from the existing database using the SQL Server management studio Generate Script tool.

   • Compare the columns of exported data with new pcs schema, remove any column from generated scripts that is no longer in new database

3. Load Data into the New Database:

   • Import data in the new database.

   • Verify all essential data, such as surveys, questions, and most importantly survey_feedback.

4. Post-Migration Verification:

   • Perform thorough testing to ensure the migrated data is correct and accessible.

   • Run reports and queries to verify that data integrity has been maintained.

5. Update IVR Endpoints:

   • Update any client applications or systems to point to the new IVR API endpoints provided by PCS 13.x.

6. Conduct Final Testing:

   • Conduct end-to-end testing of the entire system, including survey creation, response collection, and reporting.

   • Test the IVR integration to ensure it works seamlessly with the new API endpoints.