# Legacy data migration (superseded)

The direct-database migration this guide used to describe is retired. Legacy
data now enters through the HTTP import surface, which runs authorization,
validation, auditing, and plugin hooks on every row:

- Contract: the IMPORT-API wiki page (admin API token + `X-Import-Mode: true`,
  which preserves original created/modified timestamps).
- Adoption playbook for a new site: the IMPORT-ADOPTION wiki page.
- Worked reference loader (West Jefferson classic-ASP schema, 15 stages,
  idempotent and resumable): `scripts/site_imports/wjf/`.
- Full pilot sequence (stand up + import + verify + cutover):
  the PILOT-DEPLOY wiki page.