Migrate from Flexible Engine to a platform operated in France
Looking for a Flexible Engine alternative for your applications? Start by separating application requirements from infrastructure dependencies. SailOps can host containers and managed services. The purpose of an initial conversation is to check that scope with your team before you commit to a migration.
What is known about the Flexible Engine shutdown?
On 3 September 2024, 01net reported the planned closure of Flexible Engine, drawing on reporting by L’Informé and statements attributed to Orange. This is a named, dated press source, not an official announcement reproduced by SailOps.
As of 28 October 2026, we have not verified an official date for a complete shutdown in the public sources reviewed. Orange’s release notes do not establish one. Confirm the deadlines applicable to your contract with Orange Business before setting your migration schedule.
Which services could you consider migrating?
This table matches documented uses. It does not describe an automatic import or complete platform equivalence. Validate each proposed target against your application.
| On Flexible Engine | Potential SailOps target | What to check |
|---|---|---|
| Cloud Container Engine (CCE) | SailOps containers | Reuse application images and settings. Plan a fresh deployment; do not assume that the entire CCE orchestration will transfer with the application. |
| RDS for PostgreSQL | Managed PostgreSQL | Compare versions, extensions and permissions. Validate a restore on the target and test the application’s queries before switching production traffic. |
| RDS for MySQL | Managed MariaDB, after validation | This changes the database engine. Test schemas, queries, collations and authentication; compatibility with your use of MySQL is not automatic. |
| Distributed Cache Service (DCS), Redis use | Redis-compatible Valkey cache | Validate commands, clients and connectivity. SailOps does not support TLS for Valkey: check your encryption requirements before selecting this target. |
| Object Storage Service (OBS) | S3-compatible object storage | Test endpoints, credentials, permissions and object versions. SailOps object storage requires an activated billing account and is unavailable during the trial. |
| Elastic Load Balance (ELB) | Gateways | Evaluate service exposure through routes and domains. Recheck protocols and rules; do not assume your entire ELB configuration transfers unchanged. |
What changes in the way you deploy?
SailOps runs a container image. For an application already using containers, check its image, startup command, variables and persistence first. For an application installed on a virtual machine, plan containerisation before migration. Copying a VM disk does not constitute a SailOps deployment.
The documentation includes CI/CD examples for GitHub Actions and GitLab CI. Use them to prepare image building and publishing, followed by deployment. Keep functional acceptance and permission to switch production within your team’s process.
How should you organise a Flexible Engine migration?
Adapt this preparation method with the people responsible for applications, data and networking. Each step should produce a result that your team can verify.
Inventory dependencies
List applications, databases, caches, objects, domains and inbound or outbound connections. Record versions, data volumes, access requirements and contractual constraints. Separate the migration candidates from services that will remain elsewhere, and identify who signs off each dependency.
Test a representative workflow
Prepare a reproducible image and a validation environment. Run a complete business workflow with its associated services. Include background processing, persistent writes and external calls, rather than checking only the homepage. Record failures and resolve them before expanding the scope.
Rehearse the data transfer
Test a database export and restore. Verify the resulting data, permissions and query behaviour. Decide which cache contents can be rebuilt. For objects, check content and access after copying. Keep the results so the final transfer has clear acceptance criteria.
Prepare access and the cutover
Recreate the required variables and secrets. Prepare domains, routes and DNS changes. Define how writes will be handled during the final transfer, what counts as acceptance and how to return to the previous environment before making any production changes.
Validate before retiring the old environment
After the switch, check business workflows and background tasks with their owners. Compare observations against the agreed criteria. Retire the old scope only after acceptance, retention of the necessary backups and a review of the applicable cancellation terms.
How can you prepare a target budget?
Use SailOps pricing to estimate the proposed scope. Account separately for migration work, testing and a possible period running both environments. Do not compare only two totals: check the resources, storage and services each covers. Have your team validate the assumptions before making a decision.
Explore pricing and the estimatorWhen is SailOps not the right choice?
If your project requires an unchanged transfer of ECS virtual machines or a bespoke IaaS network architecture, SailOps is not a direct replacement. Its documented deployment scope is containerised applications. Do not commit to a migration before assessing the network dependencies that your applications require.
If you require SecNumCloud qualification or ISO 27001, SOC 2 or HDS certification, SailOps is not suitable today: it holds none of these. Its public documentation states this limitation. Check certification requirements at the start of the project, before investing in migration tests.
Questions to resolve before migrating
Can SailOps replace my entire Flexible Engine account?
Do not assume that it can. The proposed scope covers containers and the documented services above. Start with each application and its dependencies, then assess what can move, what needs adapting and what requires a different solution.
Can I keep a MySQL database without changes?
Do not rely on that assumption without testing. The target proposed here is MariaDB. Differences from MySQL include query behaviour, collations and authentication. Test the features your application actually uses against a representative copy before considering a production move.
Where will my data be hosted?
Data is hosted in Paris. The public documentation specifies the customer data covered and lists one available region, Paris in France. Review that location and your contractual requirements with your team before selecting the platform.
Can the migration happen without an interruption?
We do not promise that. Plan a cutover window based on your constraints, data transfer strategy and completed tests. Agree who can authorise the switch and under which conditions the team should return to the previous environment.
What should I prepare for the first conversation?
Bring an architecture diagram, a service inventory, versions, data volumes and access constraints. Include certification requirements and the deadlines Orange has communicated to you. This allows a discussion of a concrete scope, without assuming everything is transferable.
Review your architecture before the switch
Identify candidate applications, necessary changes and validation points so your team can decide what comes next.