Changing your support
You want another provider to take over. We review the environment, organise access and agree on the scope of ongoing care.
IT migration. New support. A clear plan.
We take over, migrate and modernise IT environments.We plan architecture, resources and connections, from applications to servers and networks.We test the changes and prepare cutover and rollback plans.
Choose your next stepChange starts with your situation.
A new provider, the end of a contract or a need to expand.We match the work to what needs to function after the change.
Moving your environment
You are moving services to other servers or the cloud. We plan data migration, resources, network connections and the switch to the new environment.
Modernising your environment
Your architecture or software versions need to change. We check compatibility, select resources and plan how to rebuild the environment.
Regaining control
You lack documentation, backups or clear access rules. We map the environment and dependencies, identify risks and agree on the next steps.
Choose your next step.
We can take over care, migrate a service or change its infrastructure.One project can combine several of these tasks.
Taking over care
For an environment that needs a new provider. We review its state, organise access and agree how ongoing care will be managed.
Ready for care
- State and dependency review
- Backups, access and monitoring
- Agreed terms of care
Environment migration
We move services to other servers or the cloud. We prepare resources, data and connections, test the move and plan the cutover.
A new environment
- Data and cutover plan
- Trial migration and functional tests
- Observation after launch
Modernisation
For an environment needing technical changes. We check compatibility, agree on the rebuild and test the functions you need.
A foundation for growth
- Compatibility and constraints review
- Version or architecture changes
- Acceptance and documentation
The initial conversation is free. We agree on scope and price before work begins. You can choose a one-off project or ongoing care.
A simple migration of a working website may be included in annual website care at PLN 700 net. We assess the environment and confirm the scope first. Repairs and larger migrations are quoted separately before work begins.
The plan covers more than transfer.
Moving data is one stage of the change.Compatibility, correct operation and readiness for further work also matter.
State and dependencies
We know what we are moving.
We review services, data, versions and connections. We check the available documentation and record dependencies and constraints.
Data and backups
We prepare a recovery path.
We plan the backup and recovery method for your data. We agree on synchronisation and how writes will be handled throughout the cutover.
Tests and acceptance
We check the functions you need.
We prepare test scenarios with you or the application developer. We verify data, access and key processes before completing the work.
Launch and observation
We check operation after the change.
We observe simple website migrations for 7 days and store, application or modernisation projects for 14 days. Other periods and support hours are agreed for each project.
Work and acceptance scope.
We match the scope to your service and its dependencies.Before starting, we agree on tests, cost and acceptance conditions.
| Project scope | Onboarding | Migration | Modernisation |
|---|---|---|---|
| Starting point | A new support provider for the environment | Moving services to another environment | New technology or architecture |
| State review | Access, dependencies and known issues | Source, data and configuration | Compatibility and change plan |
| Checking the result | Ready for the agreed care | Services, data and connections after the move | Environment operation after the changes |
| Completion | Handover or ongoing care | Observation and acceptance | Observation and change record |
Websites and WordPress
We move files, the database and the required configuration. We check pages, media, login, forms and the certificate. We agree on technical email and DNS records.
A domain change may require redirects and URL checks. Changing the website platform is quoted as a separate project.
Stores and order continuity
We check products, orders, accounts and integrations. We test the agreed purchase journey, delivery, notifications and payments in a safe test mode.
We agree on final synchronisation and any pause in writes. The cutover window depends on the store architecture and sales requirements.
Infrastructure, applications and business systems
We map services, servers, network connections and user access. We check background jobs and integrations.
We prepare the target resources, required versions, configuration and system startup method.
We confirm the right to run the software and database in the target environment. We check services, accounts, permissions and user access to the application. Business functions are accepted by the client or product partner.
Databases and write consistency
We treat moving a database, upgrading its version and changing the engine as different scopes of work. We choose the method for the engine, version and data size. We check roles, permissions, extensions and the application connection.
Before cutover, we agree on pausing writes or final synchronisation. After the move, we check the data and application reads and writes. The rollback plan covers new data written at the destination. Engine or schema changes require a compatibility assessment.
Modernisation and known issues
We describe issues and how changes affect the environment. Repairs, dependency updates or restructuring the environment and code are quoted after assessing the scope.
Each remaining constraint is documented with its impact on operation, security and recovery. Before taking over care, we agree on what will be fixed, what remains and what we are responsible for.
Cutover and rollback
Before starting, we confirm the work window, backup, tests and acceptable downtime. We agree which environment is the authoritative data source at each stage and the last safe point to roll back.
Rollback must also account for data written after cutover. Simply pointing traffic back to the old server may not be enough for a safe reversal.
Observation and handover
We observe simple website migrations for 7 days and store, application or modernisation projects for 14 days. Other periods and support hours are agreed for each project.
Corrections to errors caused by our migration are included in the project price. We hand over the configuration, test results, constraints and recovery instructions. We agree on ongoing responsibility and separately approve source shutdown.
Project cost and ongoing care
We assess initial needs free of charge. If a detailed paid assessment is needed, we confirm its scope and price before it begins.
The quote covers discovery, destination setup, backups, migration, tests, cutover, observation and handover. It includes required licences, product partners and the period of running both environments. Website work is PLN 100 net/hour; administration is PLN 300 net/hour. Development is quoted separately. We confirm the price before work begins.
You can choose a one-off project without a subscription or combine it with ongoing care. A monthly subscription with an onboarding fee has one month’s notice. The option without an onboarding fee has three months’ notice. We define the onboarding scope before the relationship starts.
From plan to launch.
- 01
Review and plan
We review the state, data and dependencies. We confirm scope, price, the cutover window and the acceptance test scenarios.
- 02
Prepare and test
We prepare the destination and test the migration. We check functions and readiness before switching traffic to the new environment.
- 03
Launch and hand over
We check data after the change and observe operation. We hand over documentation and agree on the next steps for ongoing support.
Questions about migration.
Is migration included in care?
One simple migration of a working website may be included in annual website care at PLN 700 net. We confirm this after assessment, before purchase.
A larger migration, repair or modernisation has an agreed quotation. For monthly subscriptions, the onboarding scope is defined before the relationship starts.
Can you migrate without downtime?
We first check how the service writes data and handles traffic. We then confirm the migration method and required work window.
We plan to limit downtime and maintain data consistency. The overall project duration is different from the time the application is unavailable.
Is a subscription required?
No. You can order one-off onboarding, migration or modernisation with documentation and agreed acceptance criteria.
If you choose ongoing maintenance, we match Standard, Business or a bespoke scope to your service needs.
What should I prepare before the conversation?
Describe the service, your goal, current provider and any important deadline. A list of applications, databases and integrations will help.
We arrange secure access before work begins. Do not enter passwords in the form.
What happens to the old server and domain?
We agree how long to keep the old environment separately from the agreed observation period. Before migration, we confirm the shutdown date and data retention.
Your domain can stay with your registrar. We agree on the necessary DNS changes and access to make them.