Inventory a community before choosing what to move
Read the guide →Guide preview
List the resources and relationships people rely on before exporting files or inviting members.
Map resources, access, responsibilities and the decision to stop.
Map resources, access, responsibilities and the decision to stop.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
List the resources and relationships people rely on before exporting files or inviting members.
Group the rehearsal by relevant access journeys, not assumptions about who will find technology difficult.
Give each retained resource a clear destination and audience before moving it.
Write the task each role needs to perform and verify the permissions that actually support it.
Preserve useful history deliberately; do not confuse copying everything with protecting continuity.
An active payment, an account and access to a space are separate facts that must be reconciled.
Publish one authoritative set of transition instructions and treat delivery, reading and successful access as different stages.
Use a representative set of member tasks to find failures before committing the whole group.
Switch the main entry route only when essential member journeys, ownership and help arrangements are ready.