...
Stages 1-2 – The existing Syndeia 3.5 SP2 environment running in production is cloned to create a new environment that is the basis for Syndeia Cloud 3.6. Syndeia admins should make the Syndeia Cloud 3.5 SP2 production deployment unavailable to Syndeia users before cloning. Syndeia 3.5 SP2 production server can be brought back online after cloning but any data created in it after cloning will not be migrated. This approach is taken to ensure that the existing Syndeia Cloud 3.5 SP2 deployment is always available as a golden starting point for the migration process.
Stages 3-68 – Syndeia Cloud 3.6 installs are downloaded, services are started, and an upgrade is performed in the cloned environment. Data is verified. The cloned environment is now the new Syndeia Cloud 3.6-based production environment.
...