From cefcefd3c863983d0d38c0bf25e45fee05f3972a Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 10 Aug 2026 13:09:00 +0000 Subject: [PATCH 1/3] docs: add step-by-step migration flow to Flightcontrol migration page --- migrate/from-flightcontrol.mdx | 41 ++++++++++++++++++++++++++++++++-- 1 file changed, 39 insertions(+), 2 deletions(-) diff --git a/migrate/from-flightcontrol.mdx b/migrate/from-flightcontrol.mdx index a7cfc31..8a8c641 100644 --- a/migrate/from-flightcontrol.mdx +++ b/migrate/from-flightcontrol.mdx @@ -132,9 +132,46 @@ Your organization has a module catalog that has our standard library of modules | **S3 bucket**
`s3` | `rvn-s3` | Buckets with policies, encryption, versioning, and lifecycle rules. | | **Job Scheduler**
`scheduler` or `fargate-scheduler` | Not available yet | Job scheduler support is still coming. | -## Migrating services +## Step-by-step migration + +There is no one-click or automatic migration from Flightcontrol to Ravion. You recreate your config in `ravion.yaml`, provision or import each module in Ravion, and cut traffic over yourself. The upside is that migration is piecemeal — you move one service at a time and both platforms keep running side by side until you're done. + + + + Sign in to [Ravion](https://app.ravion.com) with your Flightcontrol credentials, then connect your AWS account and Git repository. Full checklist in [Start here](/start-here#human-setup). + + Ravion and Flightcontrol share the same organization and memberships, but all other data is separate. + + + + Give your agent the [Docs MCP server](/mcp/overview), then paste your existing Flightcontrol config (for example `flightcontrol.json`) into the chat and ask the agent to produce a `ravion.yaml` draft. + + Point the agent at [Start here (human + agent)](/start-here) and this page so it has the mapping table above and the [project config file workflow](/config-as-code/project-config-file#agent-tips). + + Verify the draft against the mapping table before applying anything. `rvn-ecs-web` and `rvn-ecs-worker` both require an `rvn-ecs-cluster`, and `rvn-cloudfront` is now opt-in per service instead of always-on. + -Log into [Ravion](https://app.ravion.com) with your Flightcontrol credentials. + + - **Provision new in Ravion** for ECS services and static sites. It's easier to cut traffic over by updating DNS than to import running load balancers and CloudFront distributions. + - **Import existing** stateful resources like RDS, ElastiCache, S3, and CloudFront distributions you want to keep. Follow [Import into a standard module](/migrate/import-into-standard-module) or [Import into a Terraform Stack](/migrate/import-into-terraform-stack) — both include agent prompts. + + + + Apply `ravion.yaml` with a dry run first, then for real. Ravion provisions the new infrastructure alongside your Flightcontrol resources in the same AWS account. Add pipeline config so builds and deploys run on push. See [Project config file](/config-as-code/project-config-file) and [Pipelines](/pipelines/overview). + + + + Deploy the service in Ravion, verify it's healthy, then update DNS to point at the Ravion load balancer or CloudFront distribution. Leave the Flightcontrol service running until you've confirmed the cutover. + + **Do not redeploy in Flightcontrol during migration.** New deploys go through Ravion from this point on. The Flightcontrol service keeps serving old traffic until DNS moves and you delete it. + + + + Once each service is fully cut over, remove it from Flightcontrol so you're not paying for duplicate infrastructure. Stateful resources you imported into Ravion are already shared and don't need to be recreated. + + + +## Migrating services **Ravion can be used alongside Flightcontrol at the same time**. They both use the same Organization and memberships, but all other data is separate. So you can migrate piecemeal, service by service, instead of all at once. From 1b1812578b382d6a9b931584f70ea82dec21fbf0 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 10 Aug 2026 13:10:25 +0000 Subject: [PATCH 2/3] docs: split em-dash clause in Flightcontrol migration intro --- migrate/from-flightcontrol.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migrate/from-flightcontrol.mdx b/migrate/from-flightcontrol.mdx index 8a8c641..785d07e 100644 --- a/migrate/from-flightcontrol.mdx +++ b/migrate/from-flightcontrol.mdx @@ -134,7 +134,7 @@ Your organization has a module catalog that has our standard library of modules ## Step-by-step migration -There is no one-click or automatic migration from Flightcontrol to Ravion. You recreate your config in `ravion.yaml`, provision or import each module in Ravion, and cut traffic over yourself. The upside is that migration is piecemeal — you move one service at a time and both platforms keep running side by side until you're done. +There is no one-click or automatic migration from Flightcontrol to Ravion. You recreate your config in `ravion.yaml`, provision or import each module in Ravion, and cut traffic over yourself. Migration is piecemeal. You move one service at a time and both platforms keep running side by side until you're done. From 48512f51d9eff17bfb5f6f9cb6c7ad771d9ae6c3 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Tue, 11 Aug 2026 19:04:25 +0000 Subject: [PATCH 3/3] docs: address migration review feedback on FC deploys and deletes Co-Authored-By: brandon --- migrate/from-flightcontrol.mdx | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/migrate/from-flightcontrol.mdx b/migrate/from-flightcontrol.mdx index 785d07e..8ce5431 100644 --- a/migrate/from-flightcontrol.mdx +++ b/migrate/from-flightcontrol.mdx @@ -147,8 +147,6 @@ There is no one-click or automatic migration from Flightcontrol to Ravion. You r Give your agent the [Docs MCP server](/mcp/overview), then paste your existing Flightcontrol config (for example `flightcontrol.json`) into the chat and ask the agent to produce a `ravion.yaml` draft. Point the agent at [Start here (human + agent)](/start-here) and this page so it has the mapping table above and the [project config file workflow](/config-as-code/project-config-file#agent-tips). - - Verify the draft against the mapping table before applying anything. `rvn-ecs-web` and `rvn-ecs-worker` both require an `rvn-ecs-cluster`, and `rvn-cloudfront` is now opt-in per service instead of always-on. @@ -163,11 +161,19 @@ There is no one-click or automatic migration from Flightcontrol to Ravion. You r Deploy the service in Ravion, verify it's healthy, then update DNS to point at the Ravion load balancer or CloudFront distribution. Leave the Flightcontrol service running until you've confirmed the cutover. - **Do not redeploy in Flightcontrol during migration.** New deploys go through Ravion from this point on. The Flightcontrol service keeps serving old traffic until DNS moves and you delete it. + **Stop deploying anything you imported into Ravion through Flightcontrol.** Once a resource is imported, Ravion manages it, and deploying it again from Flightcontrol means two platforms changing the same resource. + + Services you provisioned new in Ravion, like ECS services and static sites, are separate infrastructure. You can keep deploying their Flightcontrol counterparts as usual until DNS moves. - Once each service is fully cut over, remove it from Flightcontrol so you're not paying for duplicate infrastructure. Stateful resources you imported into Ravion are already shared and don't need to be recreated. + Once each service is fully cut over, remove it from Flightcontrol so you're not paying for duplicate infrastructure. + + + **Never delete a service in Flightcontrol that you imported into Ravion.** Deleting it in Flightcontrol destroys the underlying AWS resources that Ravion now manages, including databases and buckets. + + Contact support instead and we'll remove the service from your Flightcontrol account without destroying anything. Self-serve delete-without-destroy is in the works. +