You do not need to move project files to use PXM. Link the folders where your projects already live, then review their runtime and service settings. Nothing happens automatically, and nothing is removed from the tool you are leaving.
Finds what you already run
- Herd
- Valet
- Homebrew
- Postgres.app
- MAMP
- Docker
Start with one project.
Pick an existing project and add it in Sites. Confirm its document root, PHP or Node version, and local address. Check that it works before moving the rest of your workspace.
Coming from Herd or Valet.
PXM reads Herd and Valet parked folders and linked sites, and detects each project's PHP pin. The discovery is read-only. Review the proposed sites and addresses, then import the ones you choose. Project files stay where they are. PXM does not read herd.yml, so review per-site settings after the import.
Local routing is a separate step. Only one app can own the HTTP, HTTPS, and DNS ports for .test at a time. Use the other app's own controls to stop its routing services, then turn on PXM's helper. Closing the other app's window may leave its background services running. There is no automatic cutover.
Coming from Sail, MAMP, or Docker.
PXM does not import Sail or MAMP projects automatically. Link the project folder, pick its PHP version, and point it at a database. For MAMP and Docker databases, Pro can discover servers on their locally published ports and either keep using them or import a copy.
Keep using your database. Pro
In Services, choose Connect Existing Database. Pick a discovered server or enter a local endpoint, provide credentials, and test the connection. Keep Current Server saves a connection without taking over the server. PXM finds servers from Herd, Homebrew, Postgres.app, MAMP, and Docker's local ports.
Or let PXM manage a copy. Pro
Choose Manage in PXM to import selected databases into a new managed service. Pause application writes for a consistent copy, review compatibility, and test your application before retiring the original. The database guide explains the boundaries of this workflow.
Node versions.
PXM installs Node side by side and honors .nvmrc and .node-version files. It does not migrate nvm, fnm, or asdf installations, and it installs no shell hooks. Set up PXM's shims and review your PATH order so the right node answers.
Update project configuration last.
After the new service is verified, update your Laravel .env or WordPress configuration, clear configuration caches, and restart long-running workers.
What PXM does not do for you.
- It does not switch local routing on its own; the other tool must release its ports first
- It does not move or delete your project files
- It does not migrate nvm, fnm, or asdf settings; pin Node per site instead
- It does not copy server-wide settings, passwords, or replication when adopting a database