You don’t need to move your project files to use PXM. Link the folders where your projects already live, then review their runtime and service settings.
Start with one project
Choose an existing project and add it in Sites. Confirm its document root, PHP or Node version, and local address. Check the site before moving the rest of your workspace.
Coming from Herd or Valet
PXM can discover parked folders and linked sites. Review the import and the proposed addresses. Existing project files remain in place. Local routing is a separate step: only one app can own the same HTTP, HTTPS, and DNS listening addresses at a time.
Use the current app’s controls to stop its routing services when you’re ready to switch. Simply closing its main window may leave background services running.
Keep using your database
In Services, choose Connect Existing Database. Select 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’s lifecycle.
Or let PXM manage a copy
Choose Manage in PXM to import selected databases into a new service. Pause application writes for a consistent copy, review compatibility, and verify your application before retiring the original server. Read the database guide for the boundaries of this workflow.
Update project configuration last
After the new service has been verified, review any changes to your Laravel .env or supported WordPress configuration. Clear application configuration caches and restart long-running workers when your project requires it.