Official migration to the new platform

# Timeline

The migration has not started. It runs in batches once the new platform reaches general availability, with no date set yet. The first batch takes newer Universal Apps, whose setup is closest to what the new platform expects. Later batches take on older apps, larger setups and apps that need code or config changes. The old platform reaches its end of life in about 2027.

# Communication

Each batch is announced by e-mail and confirmed by another one once the apps have moved. Batches are opt-out: the owner can postpone to the next wave.

# Account migration

Matching accounts are created on the new platform, identity and billing carry over:

• companies → teams
• billing contacts → payment methods
• apps have environments now (at least one)

# App migration

Steps per app, once the account is in place:

1. Apps, environments and domains pre-created and pre-configured.
2. Code, files and database copied over.
3. Review by fortrabbit staff.
4. DNS switch (see below).
5. Old app deleted soon after.

# DNS switch

fortrabbit handles the DNS switch — no downtime, no interaction. A hop points the old CNAME-based app URL at the new default domain:

domain → {{appname}}.frb.io → {{env-id}}.{{region}}.frbit.app

Pointing the domain straight at the default domain afterwards removes that hop.

# After the migration

• New dashboard at dash.fortrabbit.com↗.
• The fortrabbit-hosted Git repository is gone. Deploy through the GitHub integration, or over SSH/SFTP/rsync.
• SSH/SFTP login with username and password is gone, SSH keys are required.
• SSH/SFTP host URLs changed, pick up the new ones from the dashboard.
• See what's new and the PHP changes.

# Suggested next steps

• Review the app. We test migrated apps, but cannot know each code base.
• Download a fresh code backup from the new platform.
• Move deployment to the GitHub integration, the only Git host supported for now.

# Billing

Migration is free. The price level stays about the same, individual bills may vary. App plans map to the new components as closely as possible, see the price comparison. Both platforms bill per app and day, in arrears:

• All apps move at once: the migration month brings one invoice from each platform, after that only the new one.
• Some apps stay behind: both platforms invoice their own apps until the last one has moved. Nothing is charged twice.

# Code/config adjustments

Apps kept up to date and configured with ENV variables need no changes. Otherwise we may adjust code or config: a composer update, a framework version bump, or hardcoded config values.

# No warranties

fortrabbit tests each migrated app, but cannot know every code base. Test the app after the migration.

Changes made to the app or its content between the copy and the DNS switch can get lost. That window is kept short.

# Self-service migration

Apps can move by hand before the official migration starts, see self migration. Contact us at any point.