Migrate from CapRover to Temps
Temps connects directly to your CapRover instance, discovers the apps and one-click databases running on it, and recreates them as real Temps projects — build config, environment variables, and a live deployment included.
What Temps discovers from CapRover
- Apps, whether git-deployed, built from a Dockerfile, or running a plain image
- One-click databases
- The app's environment variables
The import creates a matching Temps project with its own environment, deploys the app for real, and — for a database Temps can reach from the machine running the import — copies its data into a Temps-managed service automatically.
Before you start
CapRover doesn't issue per-user API tokens — Temps authenticates with the CapRover admin password (the install default is captain42 until changed).
You'll also need your CapRover instance's URL (e.g. http://your-caprover-server:3000).
Step 1: Connect and discover
Discover what's running on CapRover
- 1
In the Temps dashboard, go to Projects, then click Import.
- 2
Select CapRover as the source.
- 3
Enter the instance URL and the admin password.
- 4
Click Discover Workloads.
Temps queries the CapRover API directly — nothing is created on this step.
Step 2: Review the plan
Pick the app to import and Temps shows the plan it will execute: the project name, build configuration, every environment variable it found (secrets masked), any databases it will create as managed services, and the domains it discovered.
Linking a Temps-tracked Git repository at this step is optional — Temps' own discovery already picks up the app's git source (if CapRover has one configured) independently, so this step is for connecting future git-push auto-deploys, not a requirement to proceed.
Step 3: Execute the import
Run the import end to end
- 1
Review the plan and click Execute Import.
- 2
Temps creates the project, its services, and deploys the app.
- 3
Wait for the deployment to reach a healthy state — Temps verifies the app actually answers before reporting the import complete.
Your CapRover instance keeps running the whole time — the import only reads from it. Verify the imported app on its Temps-provided address before touching DNS.
After the import
Once you've confirmed the imported app behaves correctly, add your production domain and cut DNS over — see moving the production domain. Keep the CapRover deployment running until you've verified normal traffic on Temps.
For the general import flow that applies across every supported platform, see Import an Existing Platform.