Migrating to ForgeKit

Summary

Migrating to ForgeKit is usually straightforward:

  • keep your existing project folder
  • keep your old database if you want
  • stop the old web server if it uses the same ports
  • add your project as a site in ForgeKit
  • keep developing

ForgeKit is designed to make local setup clearer, not more complicated.

Moving from Laragon, Herd, XAMPP, WAMP, MAMP, or another local setup is incredibly simple.

In most cases, you do not need to move your project files or rebuild your app.
You install ForgeKit, choose the runtimes you want to use, add your existing project as a site, and keep working.

What migration usually means

For most developers, migrating to ForgeKit is just this:

  1. Install ForgeKit
  2. Choose your preferred web server and PHP version
  3. Add a site that points to your existing project folder
  4. Open it in the browser

That’s it.

Your application code stays where it is. Your existing database can usually stay where it is too.

Before you start

Before adding sites in ForgeKit, make sure you know:

  • where your project folder lives
  • which PHP version your project needs
  • which web server you want to use
  • whether another local web server is already using port 80 or 443

If another app is already running Apache or Nginx, make sure to stop those so ForgeKit can use the ports.

Common examples:

  • XAMPP Apache
  • Laragon Apache or Nginx
  • WAMP Apache
  • IIS
  • another local dev tool already bound to port 80 or 443

The standard migration flow

1. Install ForgeKit

Install ForgeKit and open the app.

2. Pick your stack

Choose the parts you want to run in ForgeKit, such as:

  • a web server
  • a PHP version
  • optionally a database server

You only need to enable what your projects actually use.

3. Add your existing project as a site

Create a new site in ForgeKit and:

  • choose the domain you want
  • point it to your existing project folder
  • choose the web server instance
  • choose the PHP version if needed

ForgeKit will generate the local site config for you.

4. Open the site

Once the web server is running, open the site in your browser.

If your project was already working in another local environment, it should usually work here with no code changes.

Migrating from Laragon

If you are coming from Laragon, the main difference is that ForgeKit gives you a more explicit and structured setup.

Your migration is usually:

  • install ForgeKit
  • recreate the site in ForgeKit
  • point it at the same project folder
  • choose the PHP version and web server
  • stop Laragon’s web server if it is using the same ports

You do not need to move the project into a special folder unless you want to.

Migrating from Herd

If you are coming from Herd, the idea is the same.

Instead of relying on Herd’s automatic local serving flow, you add the project as a site in ForgeKit and choose exactly how it runs.

Typical steps:

  • install ForgeKit
  • add the project folder as a site
  • choose the domain you want
  • select the PHP version and web server
  • make sure Herd is not holding the same ports

If your app depends on services outside the web server and PHP, keep those running as usual.

Migrating from XAMPP or WAMP

If you are coming from XAMPP or WAMP, the biggest thing is usually port conflicts.

Your project files can stay exactly where they are.

Typical flow:

  • install ForgeKit
  • stop Apache in XAMPP or WAMP
  • add your project folder as a site in ForgeKit
  • choose the PHP version and web server
  • open the site in the browser

You do not have to migrate your database just because you changed local web server tools.

What happens to your database?

Usually, nothing.

You can often keep using your existing database setup as long as it is still running and reachable.

That means:

  • if you already have MySQL or MariaDB running elsewhere, you can keep using it
  • if your old database setup works fine, there is no need to recreate everything immediately
  • if you want a fresh setup, you can create a new database inside ForgeKit instead

Option A: keep your old database

This is the easiest path.

As long as your database server is still running and your app can connect to it, you can leave it alone.

This is useful if:

  • your old setup already has the data you need
  • you do not want to import/export databases yet
  • you are only moving the web-serving part to ForgeKit

Option B: create a new database in ForgeKit

If you want everything managed in one place, you can start a database server in ForgeKit and create a new database there.

This is useful for:

  • fresh projects
  • cleaner local setups
  • moving away from older tool-specific database installs

Port conflicts

The most common migration issue is another app already using port 80 or 443.

If ForgeKit cannot start its web server, check whether another tool is still running.

Common causes include:

  • Apache from XAMPP, WAMP, or Laragon
  • Nginx from another local tool
  • IIS on Windows

In most cases, the fix is simple: stop the other web server, then start ForgeKit again.

You can still keep the other tool installed. It just should not be actively using the same ports at the same time.

Do you need to move your projects?

No.

ForgeKit can point to your existing project folder, wherever it already lives.

That means you can keep using:

  • your current folder structure
  • your existing repositories
  • your current workflow in your editor or terminal

You are not forced into a special directory layout.

Do you need to change your code?

No.

If your app already works locally, migration is mostly environment setup, not application rewrite.

You may need small updates only if your previous tool was hiding configuration details that now need to be explicit, such as:

  • document root
  • PHP version choice
  • site domain
  • port usage
  • environment variables

Recommended migration path

For most users, this is the smoothest approach:

  1. Install ForgeKit
  2. Stop your old local web server
  3. Keep your existing database as-is
  4. Recreate your project as a site in ForgeKit
  5. Confirm the app runs
  6. Later, decide whether you also want to move the database into ForgeKit

This keeps migration low-risk and avoids changing too much at once.

Troubleshooting

The site does not open

Check that:

  • the site was added with the correct project path
  • the web server is running
  • another tool is not already using the same port
  • try localhost in the browser. If you don't see ForgeKit, then port 80 is being used by another tool

PHP looks wrong

Make sure the site is using the PHP version your project expects.

The database connection fails

Check whether your old database server is still running and whether your app is still pointing to the correct host, port, username, and password.

It worked in my old tool but not here

In most cases, the issue is configuration, not the project itself.
Double-check the document root, PHP version, and whether another local server is still active.