Migrate from Laravel Vapor to Laravel Cloud

Laravel Vapor to Cloud: Migration steps

Set up Laravel Cloud account

Create your account at cloud.laravel.com and set up your organization. Have questions? Check our Laravel Cloud Quickstart documentation.

Create your new application

1. From your Cloud dashboard, click + New application.
2. Connect your Git provider (GitHub, GitLab, or Bitbucket).
3. Select your repository and branch.
4. Configure your environment settings:
   • Choose PHP version from the list of supported versions.
   • Set environment variables (copy from Vapor UI or .env).
   • Add any secrets your application needs.

Provision your new infrastructure

Create the resources your application needs:

MySQL/Postgres database

1. In your environment's infrastructure canvas, add a Database.
2. Choose MySQL or Postgres (match your Vapor configuration).
3. Select compute size based on your needs.
4. Enable public endpoint for migration (you can disable after).
5. Cloud automatically configures Laravel environment variables.

KV store for cache/session storage

1. Add a KV Store resource to your infrastructure canvas.
2. Choose Redis or Valkey
3. Cloud automatically configures Laravel environment variables.

Object storage (S3-compatible)

1. Add Object storage if you use file uploads.
2. Update your filesystems.php configuration to use the Laravel Object Storage.

You've now set up a new Laravel Cloud account and provisioned all necessary infrastructure. You can now migrate your Vapor application to Cloud.

Prepare to migrate

1. Log into your Vapor account.
2. Get your Vapor database credentials:
   • Check Vapor dashboard → Project → Environment → Database
   • Or check your Vapor environment variables

Migrate your database

With your new Cloud database provisioned and public endpoint enabled:

Finding your Cloud database credentials:

• Cloud dashboard → Environment → Database → Connection Details
• Credentials are also injected as environment variables

For MySQL

Export from Vapor

# From your local machine
mysqldump \
  --host="vapor-db-host" \
  --port="vapor-db-port" \
  --user="vapor-db-username" \
  --password="vapor-db-password" \
  --single-transaction \
  --routines \
  --triggers \
  --events \
  "vapor-db-database" > "dump-file.sql"

Copy

Import to Cloud

# From your local machine
mysql \
  --host="cloud-db-host" \
  --port="cloud-db-port" \
  --user="cloud-db-username" \
  --password="cloud-db-password" \
  "cloud-db-database" < "dump-file.sql"

Copy

For Postgres

Export from Vapor

# From your local machine
pg_dump \
  -Fc \
  -f "dump-file.bak" \
  "postgresql://vapor-db-username:vapor-db-password@vapor-db-host:vapor-db-port/vapor-db-database"

Copy

Import to Cloud

# From your local machine
pg_restore \
  --clean \
  --no-owner \
  --no-acl \
  --if-exists \
  --dbname="postgresql://cloud-db-username:cloud-db-password@cloud-db-host:cloud-db-port/cloud-db-database" \
  "dump-file.bak"

Copy

At this point, you are ready to deploy your application to Cloud by hitting the "Deploy" button. Follow the next steps to test if everything is working correctly.

Test your Cloud deployment

Before switching DNS:

1. Deploy your application: Click the Deploy button in Cloud.
2. Verify deployment: Check the deployment logs for any errors.
3. Test using Cloud URL: Every environment gets a .laravel.cloud URL.
4. Run smoke tests: Verify critical functionality works.
5. Check background jobs: Ensure queues are processing correctly.

Switch DNS to Cloud

Once verified, point your domain to Cloud:

1. In the Cloud dashboard, go to Domains and add your custom domain.
2. Cloud will provide DNS records (A/CNAME).
3. Update your DNS provider with the new records.
4. SSL certificates are automatically provisioned and renewed.

Disable public database endpoint (optional)

After migration is complete and stable:

• Disable the public endpoint on your Cloud database for security.
• Your application will continue to access it via private network.

End your Vapor subscription

Once you've successfully deployed and tested your application, don't forget to cancel your Vapor subscription. If you were only using AWS for the application you migrated to Cloud, you can also cancel your AWS subscription since no third-party infrastructure providers are needed with Cloud.