# Connecting an existing (legacy) community

> Built a community on the classic Estage platform? Import the project into Genesis and keep it — members, content, and all.

Source: https://knowledge.estage.com/community/legacy-import/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
If you already run a community on the classic Estage platform, **don't create a new one** —
you'd be starting from zero. Import the legacy project into Genesis instead: the existing
community stays exactly as it is, and Genesis builds around it.

## What importing does

Importing creates a Genesis project **linked to your existing Estage project** — same project
identity upstream, same community, same members, same content. Genesis doesn't copy or
recreate anything; it adopts what's there.

You get the full Genesis experience on top: the AI builder for the website, publishing,
custom domains — while the community keeps running untouched.

## How to import

1. On your Genesis dashboard, click **Import Legacy** in the header (the modal says *"Import
   Legacy Project (Community, CRM, etc)"*).
2. Enter your **legacy Estage project ID** — the numeric ID of the project (you can see it in
   the classic platform's URL when the project is open).
3. Optionally pick one of your Genesis projects to copy **starter site files** from — useful
   if you've already built a site style you want to begin with.
4. Confirm.

Genesis verifies the project is **yours** (you must be signed in with the same Estage
account), then the imported project appears at the top of your dashboard.

## After importing

- **Settings → Modules** shows Community as **ENABLED** with the **Open community →** link —
  no "Add community" needed; it found the existing one.
- Build the site with the AI as usual and publish.
- Put the community on your own domain — see
  [Community on your domain](/community/custom-domain/) — e.g. move it from its legacy
  address to `community.mysite.com`.

## Notes

- **Don't click "Add community" on an imported project** — the community already exists;
  the module reflects it.
- Members and their content are untouched by the import — nothing to announce, no migration
  window.
- The import requires ownership: a project ID belonging to another account is rejected.
- **Typed the wrong ID?** You're no longer stuck with it — the project can be
  [re-bound to the correct Estage project](/project-settings/general/#re-bind-to-another-estage-project),
  files, pages, chat history and settings included.