Plan a move for websites, applications, databases or email with dependencies, validation and a rollback decision defined before cutover.
Start with a plan below, or talk to us about a custom setup.
Resources, deliverables and commercial terms confirmed against your requirements.
Commitment and billing term confirmed in quotation
Applicable taxes, software licences, migration, backups and management unless expressly included.
Choose cloud migration around a measured workload and a clear operating model.
Businesses transferring an application between providers or onto a new server configuration.
Teams assessing operating-system, database or runtime compatibility before moving data.
Organisations moving users and mail flow with domain and account ownership understood.
The quotation records the available options and the exact supplied configuration.
| Requirement | What to review |
|---|---|
| Source inventory | Applications, versions, data sizes and connected services. |
| Destination design | Resources, software compatibility and access controls. |
| Data transfer | Method, permissions, encryption and working space. |
| Change window | Business approval, traffic changes and downtime assessment. |
| Acceptance | Application checks and named business approver. |
| Rollback | Conditions, decision owner and retained source access. |
Separate the core service from work and software that need an additional agreement.
The server configuration or professional service described in the quotation. Confirm access, operating system and the agreed deliverables.
Migration, backup administration, monitoring, management and additional software need a separately agreed scope and price.
Confirm taxes, setup charges, licensing, commitment, renewal and cancellation. Availability, workload location and support commitments belong in the quotation.
A migration is more than a server copy. List databases, background workers, uploaded files, certificates, scheduled jobs, external APIs and the DNS records that direct users to the application. Identify software licences tied to an address or machine. Agree which records can change during transfer. This inventory helps the team choose a workable migration method and highlights dependencies that require a vendor or customer action outside the server move.
Prepare the destination and validate it before redirecting production traffic. Check sign-in, forms, uploads, email delivery, scheduled jobs and important reports with someone who knows the application. A homepage loading successfully does not prove that the full service works. Use a test environment or a controlled access method where appropriate. Record issues and acceptance criteria, then confirm who has authority to approve the transition.
Define the change window, communication contacts and data consistency approach. Agree how new writes are handled while data is moved and what would trigger a rollback. Keep the source available for the agreed period and make sure the team understands which environment is authoritative. Migration effort, business interruption and completion dates depend on the actual workload. They are reviewed with the scope rather than promised through a generic website claim.
The management proposal lists the environments and tasks that CloudLelo will administer. It should identify monitoring checks, maintenance approval, patching windows, backup administration and incident escalation. Your team retains responsibility for application changes, business data, access approvals and decisions about acceptable interruption. An agreed scope is essential: server management does not automatically include application development, software vendor support or unlimited incident work.
A task is assigned to CloudLelo only when it appears in the agreed management scope.
| Task | Customer / self-managed | Scoped CloudLelo management |
|---|---|---|
| Configuration | Define and administer the environment | Perform agreed configuration tasks |
| OS / account updates | Plan, test and apply required changes | Apply agreed changes in approved windows |
| Monitoring | Select checks and respond to alerts | Operate the specified checks and escalation |
| Backup administration | Arrange jobs, retention and recovery testing | Administer the agreed backup jobs and restore tests |
| Applications and data | Own code, data and business validation | Application work only where explicitly included |
| Support scope | Provide authorised contacts and useful incident detail | Follow the agreed channels and service boundaries |
Deployment dates, service commitments and acceptance criteria are agreed for your project.
List applications, versions, dependencies, usage and authorised contacts. Identify protected data and the business owner who can validate deployment.
Confirm resources, software, access, transfer, fees and the administration scope. Record commitments and exclusions before approving the quotation.
Agree migration or deployment, backup checks and acceptance tests. Define the rollback decision and retain source access until handover criteria are met.
Document credentials, ownership and escalation contacts. Review resource use, maintenance and recovery arrangements as the workload changes.
Understand the configuration and responsibilities before requesting an order.
Migration is a scoped service. Transfer effort, compatibility work and validation are priced in the quotation; it is not automatically included with a server.
Interruption depends on the application, data changes and cutover method. The migration plan assesses downtime and rollback; no zero-downtime promise is made here.
Access depends on the source, destination and transfer method. Provide the inventory first. Agree secure credential exchange after the scope has been reviewed.
The quotation identifies resources or subscriptions, selected operating work, taxes, licences and commercial commitments. Consulting and provider consumption charges are reviewed separately.
Describe the application or provider, current setup, users, data size and intended change. Avoid passwords, private keys and confidential business records.
Confirm protected data, frequency, retention, storage location and restore responsibilities separately. Provider retention features do not automatically establish an independent backup arrangement.
The approved scope lists tasks, channels, escalation and maintenance responsibilities. Any support hours or response commitments must be agreed for the service.
Changes depend on availability, software and commercial commitments. Review potential interruption, data, licences and costs before approving a resource or subscription change.
From a new server to an existing application migration, start with your workload and leave with a clearly defined scope.