Files
shopdb-flask/migrations/DATA_MIGRATION_GUIDE.md
cproudlock 99cac87d9a
Some checks failed
CI / backend (push) Successful in 1m41s
CI / naming (push) Successful in 1s
CI / frontend (push) Successful in 8s
CI / migrations-mysql (push) Failing after 8s
README: refresh to current product surface; retire direct-DB migration guide
Overview and plugin list cover all twelve plugins (geenforce, network
subnets, measuring tools, warranty, USB); naming examples use living
tables/columns instead of retired pctypes/isvnc; API params match the
implementation (perpage, dir, assettype); import section points at the
IMPORT-API surface and the wjf reference loader. DATA_MIGRATION_GUIDE
is now a pointer stub (its direct-DB approach is superseded).
2026-07-13 19:49:34 -04:00

14 lines
658 B
Markdown

# 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: `docs/IMPORT-API.md` (admin API token + `X-Import-Mode: true`,
which preserves original created/modified timestamps).
- Adoption playbook for a new site: `docs/IMPORT-ADOPTION.md`.
- 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):
`docs/PILOT-DEPLOY.md`.