A suitable environment.
The website or application is hosted with its data volume, resources and actual constraints in mind.
Check access, ownership and recovery.
Agree downtime, data, files and a recovery path.
Choose a foundation for the actual scope.
A running server alone is not acceptance.
If the current hosting fits, keep it. Before a move, agree downtime, backups, access and the recovery path.
The website or application is hosted with its data volume, resources and actual constraints in mind.
Provider services, licences, ongoing support and additional work are clearly separated.
For a migration, dependencies, the cutover window and verification criteria are defined.
The team knows who owns the domain, accounts and data, and how changes are made.
A new service needs different resources. The current server is difficult to update and only one person knows its settings. Several projects interfere with one another. Costs are rising but it is unclear which resources are really needed. In each case we first establish the cause and a useful outcome rather than choosing the largest server.
We compare options permitted by the application: a provider's service, a managed platform or your own environment. We check restrictions on extensions, access, region, storage and backups. We check capabilities and limitations for the chosen plan and hosting method.
We define the application, database, file storage, network connections and external services. We separate production and test environments where needed. Versions and dependencies are documented so the system can be supported beyond launch day.
We configure agreed roles and administrative access methods. We define ownership of accounts, the domain and data, and how permissions are granted and revoked. We do not collect passwords or keys through an ordinary enquiry form or put them in shared instructions.
We document the components, costs and change process. Monitoring, backups and failure response are agreed separately from resource rental. A ready virtual machine does not by itself mean a ready business service.
We first establish where materials and the database reside, how participants receive access and which external messages are possible. The test environment is separated from real mailings and payments. Components are chosen for the selected system and licences.
We check whether existing hosting is sufficient for the catalogue and required exchange. If the issue is enquiry handling or data, more resources alone will not fix it. We first address the confirmed constraint.
Inventory the data and dependencies, and select a window and success criteria.
Prepare the new environment and check it before cutover.
Agree the final transfer, any pause in changes and how to return if there is a problem.
After cutover, check the selected user journeys and observe the result.
We do not promise zero-downtime migration in advance: feasibility depends on the application, data, external connections and acceptable risk. Transferring an account, changing DNS and having a ready application are not one action.
| Situation | A small website or one application |
|---|---|
| Option to assess | Managed hosting or a virtual server |
| What to check | Data, access, backups and costs |
| Situation | Several closely connected services |
|---|---|
| Option to assess | Docker Compose and separate components |
| What to check | Database and file consistency, networks and updates |
| Situation | A justified requirement for multiple nodes |
|---|---|
| Option to assess | Kubernetes as a possible separate project |
| What to check | An operations team, storage, resilience and cost |
One website or Odoo application can run on managed hosting or a virtual machine. For several connected components we consider Docker/Compose, defining the application, PostgreSQL, files, network and operating settings separately. A container does not replace data backups and recovery tests, and a virtual machine does not by itself provide resilience.
We consider Kubernetes where multiple nodes and separate scaling rules are actually needed and there is a team to support the cluster. Before choosing it, we compare operating costs, recovery, access, monitoring and possible host failure. We do not call Kubernetes a mandatory part of the pNet Business Platform.
For example, an academy needs its learning materials and registrations available, while a supplier needs consistent catalogue and order data. For both scenarios pNet first designs a verifiable path and dependencies, then selects hosting and agrees support.
Note: moving a server, changing DNS and having a ready application are not one action. Most small projects do not require Kubernetes.
A description of the selected environment, agreed access and responsibility boundaries. It is clear what is paid to the provider, which work pNet performs and what needs separate support. Critical settings and restrictions are not left only in correspondence.
Hosting costs, provider choice, data location and support conditions are agreed before implementation. A move includes a return plan and checks of the data and workflows that matter to you.
Describe your systems, the problem and any known constraints. You do not need a complete technical specification. Please leave passwords, keys and customer data out of your message.
The choice depends on the task and available terms. We first assess the existing provider and project constraints, then suggest a suitable option.
No. The cause may lie in the application, data queries or an external service. We check the bottleneck before increasing costs.
Only the agreed scope. Resources, licences, support, backups and external services are shown separately.
Yes. Roles and ownership are agreed. Permissions should match responsibilities and there should be a clear change process.
Tell us which application is running or being prepared, where the data is and what constraints are causing problems. We will identify suitable components and a first step.