Migration and Import
Migration-specific reference covering import and recovery operations. This area defines how data or site state is brought into SGEN, how validation is handled, and what safeguards apply before a migrated site is treated as production-ready.
Definition
Migration and Import references describe how data or sites are brought into SGEN, how recovery is handled, and what validation needs to happen before a migrated site is treated as production-ready. This area should be read as a risk-aware reference layer rather than a day-to-day administration guide. :contentReference[oaicite:0]{index=0}
Purpose
The purpose of this page is to define the migration and import scope within the SGEN stack, clarify how import and recovery-related operations fit into the platform, and provide a stable reference model for validation, fallback, and post-migration handling. :contentReference[oaicite:1]{index=1}
Scope
This reference area covers migration and import activities that move data or site state into SGEN. It also covers safeguards, validation points, and recovery considerations tied to those activities.
Responsibilities
The Migration and Import area is responsible for making data movement and recovery-sensitive operations understandable at a platform level.
Defines how imported data or migrated site state should be understood within the SGEN platform.
Clarifies where validation needs to occur before migrated state is treated as stable or production-ready.
Documents the fallback, rollback, and recovery considerations that matter when migration work does not behave as expected.
Key elements
The Migration and Import section includes the following child pages:
Together, these pages define the migration-specific reference model used across import, validation, cleanup, and recovery-sensitive operations. :contentReference[oaicite:2]{index=2}
Operational role
In operational terms, this area exists to separate migration-sensitive work from normal administrative behavior. It provides a reference layer for activities that can affect larger site state, imported content integrity, recovery options, and readiness decisions after data movement has occurred.
Constraints and boundaries
This reference area defines migration scope, safeguards, and recovery considerations. It does not replace operational runbooks, onboarding instructions, or release communication.
Documentation guidance
Use this page as a reference definition. Task-by-task instruction, onboarding steps, or procedural walkthroughs should live in Guides, while product updates and shipped changes should live in What’s New or Changelog. :contentReference[oaicite:4]{index=4}
