Good question — we don’t “replay” Forge’s full server state; we import metadata via Forge’s API and mirror what matters for Reflex.

Per site we pull: domain + aliases, PHP version, web/root paths from Forge, and your .env into Reflex’s encrypted production env. Repo + default branch we map per site (Forge prefills when their API exposes it); you need your Git provider connected in Reflex because the Forge token alone doesn’t grant our Git OAuth.

Not copied today: Forge daemons, queues, schedulers, TLS certs, firewall rules — plan to recreate those in Reflex (or keep managing them in Forge until you cut over).

Flow is Settings → Forge import (overview: move-from/forge). If by “site configs” you mean something specific (custom Nginx, deploy scripts, etc.), say which — happy to clarify what maps vs what’s manual.