# Migrate Strapi from Railway to EasyHost Move your Strapi app in four steps, and keep Railway running until the new deployment works. ## Export your variables ``` railway variables --kv > .env ``` Then import them into EasyHost. ``` npx ezhst env import .env ``` ## Change the Strapi setup No adapter is needed. Move from SQLite to Postgres and switch uploads to an S3 provider. `railway.json or railway.toml` is not read by EasyHost, so its build and routing rules need moving into your app or into build settings. Use Postgres rather than SQLite, and set Strapi's secret variables before the first deploy. ## Deploy and test ``` npx ezhst projects create my-project --link npx ezhst apps create my-app npx ezhst link --project --app npx ezhst env set APP_KEYS=, API_TOKEN_SALT= ADMIN_JWT_SECRET= TRANSFER_TOKEN_SALT= JWT_SECRET= npx ezhst env set DATABASE_CLIENT=postgres DATABASE_URL= npx ezhst env import .env npx ezhst deploy ``` Test your `easyhost.fun` URL before changing DNS. Railway runs your app on long-running services billed by usage, so check anything that depends on it, such as platform functions or cron configuration. Schedules move to [EasyHost schedules](/guides/strapi-cron-jobs). ## Switch your domain ``` npx ezhst domains add www.example.com npx ezhst domains list npx ezhst domains verify www.example.com ``` Follow the [custom domain guides](/guides) for your DNS provider. Keep Railway running until traffic has moved. Also read [why Strapi may be unreachable](/errors/strapi-app-unreachable) and the [Railway overview](/migrate/railway).