Stay organized with collectionsSave and categorize content based on your preferences.
The Cloud Foundry to Cloud Run migration guides provide background information
on the differences between Cloud Foundry services and Cloud Run services,
and show what you need to do to migrate Cloud Foundry applications to run in a container
on Cloud Run. These migration pages do not cover data migration.
Cloud Foundry applications eligible for migration
Cloud Run is designed to run stateless HTTP or HTTP/2 applications.
Your Cloud Foundry application cannot be migrated unless it meets the following
criteria:
Uses HTTP or HTTP/2 (including gRPC).
Listens for traffic based on thePORTenvironment variable.
Doesn't require routing on different paths to different applications.
Doesn't require legacy Cloud Foundry "route services" for proxying traffic.
Doesn't require an instance ID or a particular startup order.
Doesn't need individual instances to be addressable.
Can be started without side-effects to the environment, for example,
starting a database migration.
Understanding the differences between Cloud Foundry and Cloud Run
Although Cloud Foundry and Cloud Run both share a similar source deployment
experience, there are crucial differences in how the platforms approach workload
containerization, application configuration and service definitions.
Cloud Foundry and Cloud Run differences are shown in the following table:
TheSpring Music exampleuses core components of Cloud Foundry to
rebuild Spring Music as an OCI compatible image and deploy it to Cloud Run. This sample follows thelift and shiftOCI compliancy strategy.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Cloud Foundry to Cloud Run migration overview\n\nThe Cloud Foundry to Cloud Run migration guides provide background information\non the differences between Cloud Foundry services and Cloud Run services,\nand show what you need to do to migrate Cloud Foundry applications to run in a container\non Cloud Run. These migration pages do not cover data migration.\n\nCloud Foundry applications eligible for migration\n-------------------------------------------------\n\nCloud Run is designed to run stateless HTTP or HTTP/2 applications.\nYour Cloud Foundry application cannot be migrated unless it meets the following\ncriteria:\n\n- Uses HTTP or HTTP/2 (including gRPC).\n- Listens for traffic based on the `PORT` environment variable.\n- Doesn't require routing on different paths to different applications.\n- Doesn't require legacy Cloud Foundry \"route services\" for proxying traffic.\n- Doesn't require an instance ID or a particular startup order.\n- Doesn't need individual instances to be addressable.\n- Can be started without side-effects to the environment, for example, starting a database migration.\n\nUnderstanding the differences between Cloud Foundry and Cloud Run\n-----------------------------------------------------------------\n\nAlthough Cloud Foundry and Cloud Run both share a similar source deployment\nexperience, there are crucial differences in how the platforms approach workload\ncontainerization, application configuration and service definitions.\nCloud Foundry and Cloud Run differences are shown in the following table:\n\nHow to migrate\n--------------\n\nTo migrate a Cloud Foundry application:\n\n1. [Choose a strategy for building OCI-compliant containers](/run/docs/migrate/cloud-foundry/oci-compliant-strategy)\n2. [Migrate to OCI-compliant containers](/run/docs/migrate/cloud-foundry/migrate-to-oci-containers)\n3. [Convert the manifest](/run/docs/migrate/cloud-foundry/migrate-configuration#convert-manifest-to-service)\n4. [Attach backing services](/run/docs/migrate/cloud-foundry/migrate-configuration#attach_any_backing_services)\n5. [Deploy the service to Cloud Run](/run/docs/migrate/cloud-foundry/migrate-configuration#deploy)\n\nSample migration\n----------------\n\nThe [Spring Music example](/run/docs/migrate/cloud-foundry/spring-music-migration-example) uses core components of Cloud Foundry to\nrebuild Spring Music as an OCI compatible image and deploy it to Cloud Run. This sample follows the\n[lift and shift](/run/docs/migrate/cloud-foundry/oci-compliant-strategy#modifying_cloud_foundry) OCI compliancy strategy.\n\nWhat's Next\n-----------\n\n[Choose your containerization strategy](/run/docs/migrate/cloud-foundry/oci-compliant-strategy)"]]
