SERVERS, CLOUD & IT
DeshTech helps businesses in Sri Lanka and internationally discuss server, cloud and IT requirements with clear responsibility for setup, access and ongoing care. Whether you are moving an existing workload or planning a new environment, begin with the systems your business depends on.
Our service areas cover managed servers; setup, migration and administration; hosting, backup and recovery; networking; and Microsoft 365 licensing and support. Supported platforms, delivery arrangements and coverage are confirmed for the specific environment before an engagement begins.
CHOOSE YOUR STARTING POINT
Start with an assessment of the environment, software, access and current responsibilities. Establish who handles routine changes, monitoring, patching, backups and escalation.
Plan the dependencies before moving files or changing DNS. The migration scope should include data, integrations, verification, an appropriate change window and a recovery approach.
Identify what is backed up, where copies are stored, how long they are retained and whether restoration has been checked. A successful backup job alone does not establish that an entire service can be recovered.
Separate network, identity, email and productivity requirements. Identify existing accounts and vendors so changes do not leave gaps in access or responsibility.
INFRASTRUCTURE SERVICE AREAS
Discuss ongoing administration for an agreed server environment. The scope can define monitoring, software updates, access administration, routine changes and incident escalation. Record which operating systems, applications and third-party components are supported, and which remain under the client’s or vendor’s responsibility.
Explore Managed Server ServicesPlan a new environment or a move between hosting arrangements. Discovery should capture application requirements, data, certificates, scheduled tasks and network dependencies. Agree the migration sequence, verification steps and rollback conditions before making production changes.
Explore Server Setup, Migration & AdministrationClarify where workloads run, who manages the environment and what recovery arrangements are required. Backup frequency, retention, storage location and restore verification should reflect the actual systems. Recovery targets must be agreed for the environment rather than assumed from a general hosting description.
Explore Hosting, Backup & Disaster RecoveryDiscuss how devices, users and business services need to connect. The assessment can cover the existing network, connectivity dependencies, segmentation and access requirements. Physical site work, hardware procurement and remote administration arrangements depend on location and the agreed delivery scope.
Explore Networking & InfrastructureDiscuss subscription requirements, tenant administration, business email and user access within the Microsoft 365 environment. Any migration or account change requires a clear plan for data, identity and continuity. Product availability, licensing eligibility and purchasing arrangements must be confirmed for the organisation; no vendor-partner status is implied.
Explore Microsoft 365 Licensing & SupportRESPONSIBILITY MAP
The hosting or cloud provider operates the contracted underlying services. Its product documentation and agreement determine availability commitments, physical infrastructure responsibilities and supported escalation routes.
The agreed administrator manages the systems within the contracted scope. This may include operating-system configuration, access, updates or monitoring, but the exact boundary should be written down.
The application owner remains responsible for business requirements, user decisions and approved data handling. Application maintenance and server administration may involve different people or agreements.
Name the people who can approve changes, access backups and coordinate with providers. Document escalation and recovery responsibilities so decisions do not depend on a single informal contact.
MIGRATION PLANNING
A migration begins with an inventory of the workload and its dependencies. Websites may rely on email delivery, payment services, scheduled tasks and external APIs as well as their database and files. Identify what must continue working after the move.
Agree how data changes during the transition will be handled. Define a change window, communication responsibilities and the conditions for continuing or rolling back. DNS and certificate changes should be considered alongside the application itself.
The release checklist should verify the functions that matter to the business. Downtime depends on the system and migration approach; a universal zero-downtime promise would be inappropriate. Keep the original environment available for the agreed period where the migration plan requires it.
BACKUP & RECOVERY
Identify files, databases, configuration, certificates and access dependencies. Some workloads need an application-consistent copy or a coordinated recovery sequence rather than an independent copy of individual files.
Discuss an acceptable recovery point for each important system. Backup frequency is one input, but the method, successful completion and available copies also determine what can actually be restored.
Identify the business impact of an interruption and the resources needed for recovery. Any recovery-time target must reflect the environment, provider dependencies and agreed support arrangements.
Agree a suitable restore verification method and record its date and scope. A limited file restore and a full application recovery answer different questions. Protect backup access and discuss retention and deletion responsibilities.
ILLUSTRATIVE SCENARIO
This is a generated planning example, not a claim about a completed client migration. A business wants to move its website while keeping enquiries and external services working.
A possible brief would inventory the website and its dependencies, prepare the destination environment, transfer an appropriate copy and review the agreed functions. The change plan would identify when records stop changing, how DNS is updated and what would trigger a rollback.
The handover would record the new access arrangements, backup responsibilities and escalation contacts. Actual delivery steps depend on the website, data and providers involved; the example does not establish a particular downtime, recovery result or support commitment.
ACCESS & SUPPORT
Use named accounts and the access needed for the agreed task wherever practical. Decide how privileged access is approved, protected and removed at handover. Do not place passwords, recovery codes or production connection details in a general contact form.
The support agreement should distinguish an initial response from diagnosis and final resolution. Coverage hours, emergency handling, maintenance windows and provider escalation need to be documented. Continuous monitoring does not automatically mean a staffed 24-hour help desk.
Changes to applications, licences, hardware and third-party services can fall outside routine administration. Identify exclusions and approval requirements so your team can plan additional work without assuming it is included.
SCOPE & INVESTMENT
The starting condition, number of systems, supported platforms and required coverage affect the engagement. Migration complexity, data volumes, access restrictions, recovery needs and documentation gaps can also influence the work.
Separate provider charges from professional services. Cloud resources, hosting, storage, licences, hardware and backup capacity may be recurring costs. A plan should identify who pays each provider and who controls the accounts.
To begin, share the type of environment, systems affected, known issues and intended timing. If an existing provider or administrator is involved, clarify their role and the access available for assessment. Detailed credentials can be exchanged later through an agreed secure method.
WORK WITH DESHTECH
DeshTech began in 2017, registered as a business in 2019 and incorporated as a private limited company in 2025. We work with Sri Lankan and international businesses and discuss infrastructure requirements alongside website and digital-service needs.
Ask for relevant experience and the proposed delivery responsibilities for your particular environment. Website development, application support and infrastructure administration are distinct contributions; the engagement should describe the actual work rather than relying on a broad IT label.
COMMON QUESTIONS
An assessment is needed first. Supported software, access rights, documentation, existing issues and the current provider’s responsibilities determine whether and how an environment can be accepted.
Only if the agreement says so. Server administration may cover the operating environment while application updates, content and custom features sit under a separate website or application support scope.
Downtime depends on the system, data changes and migration approach. Agree the change window, verification and recovery plan for the actual workload instead of assuming that every move can be interruption-free.
No. Backups provide copies of agreed information. A recovery plan also addresses the environment, access, dependencies, sequence and people needed to restore a useful business service.
Coverage and emergency arrangements must be confirmed in the proposed agreement. This page does not promise continuous staffed support or a universal response or resolution time.
Share the services you need, approximate user numbers and whether you already have a tenant or email provider. Licensing, migration, access and support requirements can then be assessed without sharing passwords in the enquiry.
NEXT STEP
Describe the environment, the problem or planned change, and any timing or continuity requirements. We can discuss the appropriate assessment and clarify the provider, administrator and business responsibilities before work is scoped.