When is migration needed?
Problems we help solve
Modernisation shouldn't be about simply moving problems to a new environment. We start with a dependency, a goal, and a transition plan.
- Servers are outdated or difficult to maintain.
- The company wants to move email, files or applications to the cloud.
- The current environment does not provide the required availability or backup.
- Maintenance costs are rising and there is no room for further development.
- You need to change your provider, region, platform or licensing model.
Fit
Who is this service for?
Companies modernising server rooms
We replace hardware, consolidate the environment or implement virtualisation.
Companies moving to the cloud
We plan to migrate to Azure, AWS or Microsoft 365 services.
Systems changing companies
We transfer databases, applications, email and files while maintaining dependencies.
Companies after takeover or change of supplier
We organise the environment, access and documentation before further development.
Service scope
What does migration and modernisation involve?
Analysis and design
We check current systems and design the target environment.
- inventory and dependencies,
- RTO/RPO requirements,
- schedule and maintenance windows.
Servers and virtualisation
We transfer local and virtual systems.
- VMware, Hyper-V and Proxmox,
- Windows, Linux and databases,
- consolidation and capacity plan.
Email, files and the cloud
We modernise the work and cooperation environment.
- Microsoft 365, Exchange and Google Workspace,
- SharePoint, OneDrive and NAS resources,
- configuration of domains and permissions.
Switching and stabilisation
We control the change and check the result.
- pilot and recovery tests,
- rollback plan and communication,
- monitoring, documentation and optimisation.
Outcomes
What will you receive?
- description of the target architecture and dependencies,
- migration plan with stages and checkpoints,
- tested switchover or rollback plan,
- stabilisation, monitoring and documentation,
- recommendations for further optimisation of the environment.
The final scope depends on the type of system, number of users and required continuity of operation.
Delivery approach
What does the project implementation look like?
- Inventory. We list systems, data, users and dependencies.
- Target project. We determine the architecture, requirements and security method.
- Pilot. We test the process in a limited part of the environment.
- Preparing the switchover. We determine the window, communication, backup and rollback.
- Migration. We transfer data or services according to an approved plan.
- Stabilisation. We monitor performance, fix problems and provide documentation.
Ways to work with us
How can we work together?
Project from analysis to implementation
We are responsible for the plan, execution, testing and handover.
Selected stage of migration
We join the project as technical support or second line.
Modernisation with further maintenance
After the change, we can take over monitoring and administration of the environment.
Supplier plan audit
We verify assumptions, risks, costs and sequence of work.
Change security
How do we reduce risk?
- We do not start the switch without a confirmed copy and a rollback plan.
- We test applications and user access before the project is completed.
- We make changes within agreed maintenance windows.
- We communicate limitations, dependencies and possible impact on work.
- After migration, we monitor the environment and document the configuration.
Responsibilities and exclusions
What may require separate arrangements?
The project scope includes agreed systems and data. Purchase of equipment, licences, installation work, cabling, supplier changes and specialised tests may require a separate quote. The timescale depends on the availability of information, tests and decisions on the client's side.
Cost
What does the project price depend on?
The factors include the number of systems and users, the amount of data, the complexity of dependencies, the required maintenance window, tests, the scope of documentation, licences and the need to work outside standard hours.
FAQ
Frequently asked questions
Can the migration take place without downtime?
In many cases, disruption can be reduced through replication, piloting, and phased transitions. It depends on the system and the required data consistency.
Do you migrate to the cloud?
Yes, we analyse the local, cloud and hybrid variants and select the model to suit the company's systems and way of working.
Are you preparing a rollback?
Yes. For changes with a significant impact, we define the conditions, sequence and possibility of return.
Can you migrate just email or files?
Yes. The scope may concern one service, e.g. Exchange, Microsoft 365, SharePoint or a selected database.
Who tests applications after migration?
We perform technical tests together with people indicated by the client who know the business process.