Migration To Cloud Process:
Based on your existing environment, the migration process includes the following tasks scheduled over 1 to 4 weeks:
Phase 1: Initial Conversion/Migration (2 to 5 days)
- You will perform a complete site backup of your current file system and databases and will provide a copy to PaperThin. Note for customer running Oracle instead of providing a database backup we may instead have you run our database conversion process pointing the destination to our database in the Cloud.
- PaperThin will restore the file system and/or database backups to a PaperThin CommonSpot instance.
- PaperThin will upgrade your site from to the latest version of CommonSpot
- PaperThin will back up the site file system and databases.
- PaperThin will install and configure a new Authoring Server and Read-Only Production Server in the Cloud.
- PaperThin will restore the file system and database backups to the Cloud servers
- PaperThin will configure Amazon firewall and load balancer to route traffic between the Authoring Server and ROPS
- PaperThin will provide you URLs to perform content testing of the site migration, development of redirect URLs, load testing, authentication testing, etc.
Estimate Time to Complete: Two (2) to five (5) days
Phase 2: Testing (2 to 10 days)
- PaperThin will run a utility to rebuild each page. Any rendering errors will be captured in a log file.
- PaperThin will perform cursory testing to ensure that main pages load fine and basic authoring functionality works as expected.
- PaperThin will evaluate the log file and will evaluate any new errors. Errors in custom code will be passed to your team for evaluation/resolution, while CommonSpot specific errors will be passed to PaperThin engineers.
- You will thoroughly test page rendering and authoring functionality.
- Any issues found will be reported immediate via a shared Google document.
Estimate Time to Complete: Two (2) to ten (10) days
Phase 3: Issue Resolution / Retesting (2 days to 10 days)
- Both teams will work to address critical errors found during testing, as appropriate.
- As fixes/changes are made, a list of changes will be kept in a shared Google document so that these changes can be applied in the same manner during the final migration.
- Once all the critical issues have been resolved and tested and you are comfortable with the state of your site(s), a mutually agreed to date in the near term will be determined to perform the final migration.
Estimate Time to Complete: Two (2) to ten (10) days
Phase 4: Final Migration & Testing (1 to 3 days)
- You will disable Authoring on your current production site(s) and both parties will re-perform all of the steps outlined in Phase 1 on new server instances.
- All fixes/changes performed in Phase 3 will be applied.
- PaperThin will perform cursory testing to ensure that main pages load fine and basic authoring functionality works as expected.
- PaperThin will re-run the utility to rebuild each page, capturing all page rendering errors in a log file.
- PaperThin will evaluate the log file, passing any errors in custom code to you.
- PaperThin will fix any critical CommonSpot or configuration issues.
- You will be responsible for thoroughly testing the site and authoring functionality.
Upon final approval, you will update your DSN entries to point to the provided CommonSpot Cloud load balancers to go live. Shortly after, PaperThin will build a new Development instance(s) from a clone of the newly tested and deployed site.
Estimate time to Complete: One (1) to three (3) days.