---
title: "Migrate from another process manager"
url: https://devlanes.run/docs/how-to/projects/migrate/
description: "Have a coding agent turn an mprocs, Procfile, process-compose, pm2, tmuxinator, concurrently or Compose setup into a project file."
updated: 2026-11-16T04:05:09.000Z
---

# Migrate from another process manager

Use this guide when mprocs, a Procfile, process-compose, pm2, tmuxinator, concurrently or Docker Compose runs your dev processes today. A coding agent with the devlanes skill does the migration; paste this into it from the repository.

```prompt
Install the devlanes skill:
npx skills add devlanes-run/devlanes --skill devlanes

Then install devlanes on this machine, set up everything it needs,
and help me port this project to devlanes from whatever runs it today.
```

::example{slug="workflows-mprocs-migration"}

## Check what the agent wrote

The agent keeps the old files, so people who do not use devlanes keep their setup. Its project file follows these rules:

- A process that keeps running becomes a service with a ready check.
- A command that ends by itself, such as an install or a migration, becomes a task.
- A container stays in its Compose file, which the project file runs under `infra`.
- A fixed port becomes the port devlanes gives the service in each lane.

```text title="Procfile.dev"
web: bin/rails server -p $PORT
```

```yaml devlanes
services:
  web:
    run: bin/rails server -p $PORT -b 127.0.0.1
    hosts: "${{ lane.domain }}"
    ready:
      http:
        path: /up
```

## Stop the old reverse proxy

If Caddy, nginx or Traefik served the project until now, the devlanes proxy takes its place, and the old one has to let go of ports 443 and 80. While its container runs, lane URLs carry port 8443, and an app that builds its URLs without a port gets them wrong. Remove the container, then restart the daemon so its proxy takes the ports:

```console title="~/dev/myapp"
$ docker compose rm -sf caddy
$ devlanes daemon restart
```

[Choose the proxy's ports](/docs/how-to/hostnames/proxy-ports/) shows how to check which ports the proxy has.

## Settings that do not carry over

The agent lists the ones your setup had:

- Restart policies, because a failed service stays failed with its error ([The daemon](/docs/concepts/daemon/)).
- Dependencies between services, because services do not wait for each other ([Start order and readiness](/docs/concepts/start-order/)).
- Loading `.env` into every process ([Read .env values and pin tool versions](/docs/how-to/projects/env-files-and-tools/)).
- Log files and terminal layouts, because devlanes keeps each service's output.

## If you would rather write the file yourself

[Add devlanes to a project](/docs/how-to/projects/add-devlanes/) goes through it step by step.

## Related

- [Run scripts your project already has](/docs/how-to/projects/run-scripts/)
- [Share one database server between lanes](/docs/how-to/infra/shared-database/)
- [`services.<name>.stop`](/docs/reference/config/project/services/#services-name-stop)
