Managed Retreat

Withdraw or relocate an exposed subject into a viable receiving zone—and release or move blocking boundaries—before an advancing front closes the remaining corridor.

Summary

Managed Retreat is the intervention pattern for a position that remains workable today but is losing room to an advancing pressure front. A habitat, community, asset, service, platform, or capability is compressed against a rear boundary that appears fixed. Because movement takes time, waiting for visible failure can eliminate the route, destination, bargaining power, and continuity needed for an orderly transition.

The solution is not simply “leave.” It is to make the closing geometry explicit, identify what is truly fixed, protect a viable receiving state and connected path, precommit a trigger, move long-lead and low-mobility elements in stages, preserve rights and essential continuity, and complete decommissioning so exposure is not recreated. Retreat is managed only when it preserves agency and viability better than unmanaged displacement would.

Structural Model

The archetype has four load-bearing objects: an exposed subject, an advancing front, a fixed rear constraint, and a remaining viable band. The band can be geographic, technical, institutional, financial, ecological, or operational. Closure occurs when the band becomes narrower than the subject’s minimum viability requirement or when its route to a receiving state is severed.

A useful planning approximation is:

closure horizon ≈ remaining viable space ÷ relative closure rate

Orderly retreat must begin before that horizon falls below the complete transition lead time plus an uncertainty and governance margin. The formula is not a forecast promise. Its value is to force comparison between how fast options are disappearing and how long acquisition, permission, trust, infrastructure, ecological establishment, data transfer, or dependency migration actually takes.

Intervention Logic

1. Define the subject and its minimum viable conditions.
2. Map the advancing front, rear constraint, pinch points, and uncertainty.
3. Estimate the closure horizon and full transition lead time.
4. Test whether the front can be attenuated or the rear boundary released before assuming relocation is necessary.
5. Specify and reserve a receiving zone that remains viable under future conditions.
6. Secure an end-to-end corridor for the least mobile or most stateful required element.
7. Establish trigger, authority, funding, participation, appeal, and reassessment rules.
8. Move long-lead dependencies first, using staged waves and parallel operation where necessary.
9. Provide support, compensation, restoration, and rights safeguards.
10. Decommission the relinquished zone and prevent renewed lock-in.
11. Monitor the front, corridor, destination, continuity, and distribution of burden until completion.

Key Components

Component	Description
Exposed Subject and Viability Requirement ↗	Identifies the habitat, population, asset, service, capability, institution, or other subject whose viable operating space is being compressed, together with the minimum conditions it must retain. The subject may be physically immobile, slow to migrate, socially rooted, technically stateful, or costly to relocate. Viability must be specified before designing movement so retreat does not preserve location while destroying function, identity, connectivity, or essential service.
Converging-Boundary Model ↗	Represents the advancing pressure front, the fixed or slowly moving rear constraint, the remaining viable band, and the subject caught between them. The model is what distinguishes managed retreat from generic relocation. It should show relative motion, uncertainty, local bottlenecks, discontinuities, and whether acting on the front, rear boundary, subject, or corridor can reopen a viable option.
Wavefront Indicator ↗	Tracks the location, speed, intensity, and uncertainty of the advancing hazard, demand, obsolescence, conflict, ecological, or regulatory front. This reuses the indexed Wavefront Propagation Management component. In this archetype it informs withdrawal timing; it does not imply the front itself can or should be controlled.
Fixed Rear Constraint Map ↗	Identifies the infrastructure, ownership, policy, topology, dependency, geography, budget, or institutional commitment that blocks movement away from the advancing front. A rear boundary is often socially or technically fixed rather than physically immovable. The map must distinguish genuinely immutable constraints from commitments that can be bought out, relocated, softened, reconfigured, or governed differently.
Closure-Horizon Estimate ↗	Estimates when the remaining viable space or transition corridor will become too narrow, fragmented, unsafe, unaffordable, or politically unavailable for an orderly retreat. The estimate should combine remaining room, relative closure rate, transition lead time, uncertainty, and decision delay. It is a planning horizon, not a promise of precise prediction.
Retreat Trigger Rule ↗	Defines the evidence and threshold for committing to withdrawal before forced displacement or corridor loss makes the transition more harmful and less reversible. The trigger should be agreed before acute pressure and should include both go and reassessment conditions. Waiting for certainty usually consumes the very option the rule is meant to preserve.
Migration Path ↗	Provides the connected route by which the subject, its functions, dependencies, or successor state can move from the closing zone to the receiving zone. This reuses the indexed Migration Path component. The path must be feasible for the least mobile or most stateful part of the subject, not only for the easiest asset or most resourced participant.
Receiving-Zone Specification ↗	Defines the destination, fallback boundary, or successor configuration that can sustain the subject after retreat under expected future conditions. A destination is not viable merely because it is farther from the current front. It needs capacity, legal and social legitimacy, ecological or technical compatibility, access, continuity, and protection against transferring the same squeeze elsewhere.
Corridor Connectivity Guard ↗	Preserves continuous, usable connection between the exposed position and the receiving zone throughout the transition. Mapped room can be illusory when a single parcel, interface, crossing, dependency, jurisdiction, or trust boundary blocks movement. The guard should test end-to-end capacity, timing, accessibility, and failure domains.
Staged Retreat Sequence ↗	Orders preparation, partial movement, parallel operation, transfer of dependencies, cutoff, decommissioning, and stabilization so retreat occurs before closure without unnecessary abruptness. Sequencing should move the longest-lead, least-mobile, most safety-critical, or most path-dependent elements early enough to keep the remainder movable. A single final move is often too late.
Transition Support ↗	Provides financial, technical, logistical, social, ecological, training, accessibility, and coordination support needed to make movement genuinely possible. This reuses an indexed component. Retreat without support selectively preserves the options of actors with resources and converts planning into inequitable forced displacement for everyone else.
Continuity Criterion ↗	Specifies which functions, relationships, services, identities, ecological processes, records, or rights must remain continuous across the move. This reuses the indexed Continuity Preservation component. Continuity may require overlapping operation, linked habitat, data/state transfer, cultural access, or staged service handoff rather than simple physical relocation.
Stakeholder Impact Review ↗	Evaluates who bears the costs, loses access, gains value, faces coercion, or receives compensation under each retreat and no-retreat option. This reuses an indexed component. The review must include people and systems with low mobility, weak bargaining power, cultural or place attachment, nonmarket dependencies, and downstream exposure.
Decommissioning and No-Reoccupation Rule ↗	Governs safe closure, removal, restoration, archival transfer, and restrictions on rebuilding or recommitting inside the zone being relinquished. Without this rule, retreat can create repeated loss cycles, stranded hazards, false expectations of return, or new sunk-cost lock-in. Exceptions need explicit evidence and sunset conditions.
Retreat Monitoring and Update Loop ↗	Updates front behavior, rear-boundary flexibility, corridor health, receiving-zone capacity, transition progress, distributional impacts, and residual exposure as conditions change. Managed retreat is not a one-time forecast and plan. The loop should support acceleration, pause, route change, additional support, or destination revision while protecting the closure deadline.
Accountable Retreat Authority ↗	Holds decision rights and accountability for trigger interpretation, corridor protection, funding, coordination, rights safeguards, destination readiness, and completion. Authority should be strong enough to coordinate across boundaries but constrained by transparent criteria, participation, appeal, audit, and conflict-of-interest controls. Diffuse responsibility is a common reason closure horizons are missed.

Optional Supporting Components

Propagation Map

Maps plausible front trajectories and spatial or network pathways under multiple scenarios. This reuses the indexed component from Wavefront Propagation Management and is useful when the advancing pressure is heterogeneous, branching, or sensitive to intervention.

Response Timing Window

Defines the interval in which orderly retreat remains feasible and retains meaningful advantages over emergency movement. This reuses an indexed component. It should be narrower than the physical hazard-arrival estimate when acquisition, approval, migration, restoration, or trust-building lead times are long.

Capacity Reserve

Maintains spare destination, corridor, staffing, financing, storage, transport, or parallel-operation capacity for uncertain movement demand. This reuses the indexed Path Redundancy Provisioning component. Capacity should not be fully consumed by ordinary growth before the retreat cohort arrives.

Salvage Value Map

Identifies what can be moved, repurposed, transferred, archived, restored, or intentionally left behind at each stage. This reuses the indexed Escalation Exit Gate component. Salvage planning can finance transition and reduce waste, but it must not delay movement past the closure horizon.

Rollback or Contingency Rule

Defines fallback action when the receiving zone, corridor, funding, front forecast, or staged transfer fails during retreat. This reuses an indexed component. Full rollback may be impossible once closure advances, so contingencies should emphasize alternate destinations, temporary staging, and protected minimum continuity.

Parallel Operation Window

Allows old and new locations, systems, services, or configurations to operate concurrently while dependencies and users transfer. This reuses an indexed component. Parallel operation reduces discontinuity but costs capacity and can prolong attachment to the closing zone if the cutoff criterion is weak.

Rear-Boundary Release Option

Specifies how a supposedly fixed rear constraint could be moved, removed, made permeable, purchased, reconfigured, or temporarily opened to create room. Some retreats can preserve the subject in place by releasing the blocking boundary rather than moving the subject itself. This option should be tested before assuming displacement is inevitable.

Compensation and Restoration Support

Funds transition burdens, loss recognition, destination adaptation, ecological restoration, and repair of harms that cannot be avoided through design alone. Compensation is not a substitute for consent or safe design. It should be timely, accessible, distributionally fair, and paired with long-term monitoring where losses unfold after movement.

Common Mechanisms

Mechanisms implement particular parts of the retreat program. A buyout, setback, corridor, migration plan, or dashboard is not the archetype by itself. The full pattern requires a closing-option diagnosis, trigger, viable destination, continuity path, support, and post-exit governance.

Mechanism	Description
Closure-Horizon Dashboard ↗	Fuses front position, remaining viable width, corridor health, and trigger status into one continuously updated read of how much time the option to retreat still has.
Setback Requirement ↗	Mandates a fixed physical or legal distance between an activity and a hazard or boundary line, so encroachment and ordinary error can't reach the harm line.
Rolling Easement or Boundary Policy ↗	Lets the protected boundary migrate landward by standing rule as the front advances, so retreat happens continuously and automatically instead of as a fought, one-time relocation.
Migration Wave Plan ↗	Breaks the retreat into sequenced cohorts with an explicit order, cadence, and cutoff for each, moving the longest-lead and least-mobile elements early enough to keep the rest movable.
Migration Readiness Assessment ↗	A pre-stage go/no-go check that a tested fallback exists and every continuity provision is in place, so a cohort commits to moving only when it could still safely turn back.
Transition Support Plan ↗	Makes the move genuinely possible for those least able to bear it—funding, logistics, case management, and compensation—so retreat preserves everyone's options, not only the well-resourced's.
Receiving-Zone Reservation ↗	Locks down the destination — land, capacity, slots, or rights — before ordinary demand or speculation consumes it, so a viable place to retreat to still exists when the trigger fires.
Controlled Corridor ↗	Holds open one protected, admission-controlled passage between the closing zone and the destination, and keeps proving it is passable end to end while the space around it constricts.
Standby Transport Corridor ↗	Keeps a pre-qualified alternate route between the reserve and the fronts continuously ready and health-checked, so a redeployment can still complete inside its window when the primary path fails.
Phased Buyout or Transfer Program ↗	Converts fixed ownership into a funded, voluntary, staged exit while the positions still hold value — so retreat isn't a fire sale forced by the emergency.
Decommissioning and Restoration Runbook ↗	The step-by-step procedure for safely closing, salvaging, and restoring a relinquished zone after exit, so the vacated position leaves no stranded hazard, no lost value, and no false promise of return.
No-Rebuild or Reoccupation Rule ↗	Bars new commitment in the zone being given up — unless an evidence-based, sunset-limited exception is granted — so the ground is relinquished once, not lost again and again.
Parallel Site or System Run ↗	Runs the old and the new configuration side by side long enough to move every dependency and prove continuity before the old one is cut off.
Assisted Migration or Translocation Plan ↗	Deliberately moves a place-bound, slow-migrating subject—a population, habitat function, or stateful system—into prepared, compatible receiving conditions when it cannot get there on its own in time.
Retreat Trigger Exercise ↗	Rehearses the withdrawal go-decision before the crisis — who reads the trigger, who invokes the authority, and how the team commits in time — so the call isn't improvised as the corridor is closing.

Parameter and Tuning Dimensions

Relative closure rate

Measure how quickly the front and rear constraint are converging, not merely how fast the front moves. A rear boundary can also advance through development, dependency growth, policy hardening, cost escalation, or loss of interoperability. Use scenario ranges rather than a single date.

Minimum viable width or operating envelope

Specify the space, connectivity, capacity, compatibility, rights, or resource conditions the subject needs. The relevant threshold may be reached before physical contact—for example when access, insurance, support, ecological exchange, or maintenance becomes nonviable.

Transition lead time

Count acquisition, planning, participation, legal approval, design, construction, ecological establishment, data/state transfer, training, logistics, parallel operation, validation, and decommissioning. Political and trust-building lead times are often longer than technical move time.

Trigger band and uncertainty margin

A trigger band should include conditions for preparing, committing, accelerating, and emergency override. The uncertainty margin should increase when front behavior is nonlinear, corridor bottlenecks are fragile, or governance delay is likely.

Rear-boundary flexibility

Classify constraints by what can change: physically immovable, legally movable, financially purchasable, technically reconfigurable, institutionally negotiable, or politically contested. Treating all current commitments as fixed can manufacture displacement.

Corridor continuity and capacity

Evaluate the weakest segment. Width, throughput, access, timing, jurisdiction, trust, interoperability, ecological suitability, and failure-domain independence all matter. A path that works only for the easiest mover is not a complete retreat corridor.

Receiving-zone capacity and future exposure

Reserve enough capacity for the incoming subject and its dependencies without displacing existing users or exceeding carrying capacity. Test the destination against the same future front dynamics that invalidated the original position.

Sequencing and parallelism

Move longest-lead, least-mobile, and most dependency-rich elements early. Parallel operation reduces cutover risk but consumes capacity; set an explicit duration and exit criterion.

Support and compensation intensity

Scale support to mobility constraints, loss, cultural and social continuity, accessibility, ecological preparation, and unequal bargaining power. Average-cost programs can systematically strand the actors facing the highest transition burden.

Salvage, restoration, and no-reoccupation policy

Determine what will be transferred, archived, reused, removed, restored, or left. Align land-use, funding, insurance, technical standards, and institutional memory so short calm does not restart the exposure cycle.

Invariants to Preserve

• A viable destination and complete path exist before irreversible departure.
• The least mobile required element is not silently excluded from the plan.
• Essential function, rights, identity, ecological connectivity, and obligations are preserved to the agreed standard.
• The destination does not reproduce or export the original hazard and overload.
• Trigger evidence, uncertainty, authority, participation, and appeal remain transparent.
• The corridor remains usable until the transition is complete.
• The relinquished zone is safely decommissioned and not quietly recommitted.
• Retreat remains distinct from abandonment, discriminatory exclusion, or sacrifice without transfer.

Target Outcomes

• Movement occurs before emergency conditions eliminate choice.
• Forced displacement, stranded cost, fragmentation, and continuity failure decline.
• More function, identity, connectivity, and salvage value survive the transition.
• Receiving capacity is prepared rather than improvised under crisis.
• New lock-in inside the closing zone is prevented.
• Burdens and support are distributed more fairly.
• Completion includes restoration, closure, and durable no-reoccupation governance.

Neighbor Distinctions

Neighbor	Why it is close	Why Managed Retreat remains distinct
Wavefront Propagation Management	Both observe an advancing front.	Wavefront management acts on the front; Managed Retreat acts on the trapped position, rear boundary, corridor, and receiving state when the front may persist.
Safety Margin Design	Both preserve distance from failure.	A safety margin is usually static headroom; Managed Retreat governs a moving boundary pair and an eventual change of position or configuration.
Flow Diversion / Rerouting	Both use paths and movement.	Rerouting redirects active flow; Managed Retreat transfers a place-bound or stateful subject and includes destination viability, continuity, and decommissioning.
Path Redundancy Provisioning	Both protect routes.	Redundancy creates backup paths; Managed Retreat is triggered by a closing position and requires the subject to leave or the rear boundary to move.
Option Preservation	Both value future choices.	Option Preservation delays commitment; Managed Retreat exercises the option before waiting destroys it.
Controlled Phase Transition	Both stage change.	Controlled Phase Transition is generic; Managed Retreat is directional and defined by front, rear constraint, and closure horizon.
Creative Destruction Management	Both may replace old structures.	Creative destruction is renewal through replacement; Managed Retreat can be necessary even when nothing superior is replacing the old position.
Escalation Exit Gate	Both resist sunk-cost continuation.	An exit gate decides whether to stop; Managed Retreat designs where, when, and how viability and obligations move.
Sacrifice Periphery To Defend Core	Both may yield ground.	Sacrifice permits intentional loss of the periphery; Managed Retreat normally transfers or preserves the subject rather than merely abandoning it.
Defensible Foothold Expansion	Both manage territory and constraints.	Foothold expansion moves outward from a protected base; Managed Retreat moves out of a closing position into reserved receiving space.

Variants

Rear-Boundary Setback

Move or soften the blocking rear boundary so the subject can shift while preserving more of its existing continuity. Rolling easements, infrastructure relocation, and negotiated boundary release are common mechanisms.

Subject-Relocation Retreat

Move or reconstitute the subject in a prepared receiving zone when the enclosure cannot be opened enough. Destination fit, state transfer, support, and loss during movement become central.

Rolling Retreat Corridor

Maintain a connected band that itself shifts through time. This is especially important for ecological migration and gradual relocation where intermediate states must remain viable.

Staged Functional Withdrawal

Transfer functions and dependencies in sequence rather than moving one monolithic object. This variant is common in infrastructure, software, institutions, and public services.

Tradeoffs and Failure Modes

The archetype trades visible early cost for lower expected forced-displacement cost. That trade is politically difficult because the benefits are avoided losses and preserved options. Corridor reservation can look inefficient during ordinary periods; parallel operation can look duplicative; and trigger rules can appear rigid. These costs should be compared with the full emergency, continuity, equity, restoration, and stranded-investment burden of waiting.

The dominant failures are trigger paralysis, paper corridors, destination mirages, selective mobility, dependency fragmentation, new lock-in, risk transfer, permanent parallel limbo, premature abandonment, reoccupation cycles, coercive displacement, and forecast overconfidence. Each indicates that one of the load-bearing parts—timing, path, destination, support, continuity, governance, or closure—was treated as optional.

Examples

Coastal habitat migration

A wetland trapped between rising water and hard development receives a connected landward reserve, rolling boundary rules, selective infrastructure relocation, and restoration of vacated areas. The program triggers on habitat-width and lead-time bands rather than waiting for complete habitat loss.

Public infrastructure transition

A low-lying emergency-services campus is migrated in waves to higher ground. Records, communications, utilities, staffing, and public access run in parallel until the receiving site passes readiness criteria. The old site is decommissioned and converted to flood storage rather than rebuilt.

Platform end-of-life retreat

An organization freezes new dependencies on an aging platform, reserves successor capacity, transfers state and users in cohorts, validates interfaces, supports affected teams, and shuts down the old environment before vendor support and security compatibility close the orderly migration window.

Ecological assisted movement

A slow-dispersing population is provided a connected upslope habitat corridor and, where needed, staged translocation. Destination ecology, disease risk, genetics, and receiving-community effects are monitored over time.

Non-Examples

• A static setback from a stable hazard boundary.
• A one-day detour around a blocked route.
• Emergency evacuation without a long-term receiving state.
• Canceling a project after a stop-loss review.
• Abandoning a low-power population or peripheral service to reduce cost.
• Calling any decline or budget squeeze “coastal squeeze” without the front–rear–corridor structure.

Review Note

Human displacement and community relocation require heightened review. The archetype is not permission to optimize people out of place. It is valid only when rights, participation, cultural and social continuity, receiving-community capacity, fair support, and alternatives are treated as structural requirements. Reviewers should also test the boundary with the unaccepted reconciliation candidate legacy_sunset_and_migration and decide whether Managed Retreat is a broad parent, a distinct neighbor, or should remain focused on converging-boundary cases.

Compression statement

When a habitat, population, asset, service, or capability is trapped between an advancing pressure front and a fixed rear constraint, model the relative closure, estimate the last orderly transition window, test whether the front or rear boundary can be changed, secure a connected path and viable receiving zone, trigger staged movement before the option disappears, preserve essential continuity and rights, decommission the relinquished zone, prevent reoccupation, and update the plan as the front, corridor, and destination change.

Canonical formula: remaining viable space = rear boundary position − advancing front position − minimum viability width; closure horizon ≈ remaining viable space ÷ relative closure rate; commit when closure horizon ≤ transition lead time + uncertainty margin

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (6)

• Boundary: Defines system limits.
• Coastal Squeeze: An immobile subject is compressed between an advancing front and a fixed rear, with no exit.
• Constraint: Limits possibilities to guide outcomes.
• Managed Retreat: Withdrawing deliberately and in advance to a defensible boundary when the cost of holding a position rises past its value, before forced displacement closes the option.
• Optionality: The asymmetric value of having a choice—bounded downside, unbounded upside—without obligation to act.
• Reversibility Horizon: Temporal threshold where reversal cost exceeds forward commitment.

Also references 33 related abstractions

• Adaptation: Systems adjust to conditions.
• Beachhead Market: A narrow defensible foothold held to fund expansion into a larger territory.
• Carrying Capacity: The sustainable load envelope of a system: the maximum demand it can carry indefinitely before sustained operation begins consuming its own substrate and lowering future capacity.
• Configuration Drift: The silent, monotonic divergence between a system's recorded intended state and its actual running state, driven by accumulated out-of-band changes that bypass the record until a forced reconciliation exposes the gap.
• Consent: Voluntary agreement.
• Continuity: Smooth change without jumps.
• Controlled Reentry: Re-establishing a suspended activity or state through staged, monitored steps with the capacity to abort, because returning to normal is a separate engineered process and not a simple reversal of the exit.
• Diffusion: Spread over time.
• Ecotone: A transitional zone of measurable depth where two regimes overlap and mix, generating gradients, elevated exchange, and zone-specific structure that neither regime alone hosts.
• Edge Effect: Where two regimes meet, a thin high-gradient band forms a distinct third regime with its own resident phenomena, absent from either interior.

▸ Show 23 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Rear-Boundary Setback · implementation variant · recognized

Moves, removes, softens, or makes permeable the fixed rear constraint so the exposed subject retains room to shift away from the advancing front.

• Distinct from parent: The parent permits subject relocation, corridor creation, or boundary release; this variant makes rear-boundary flexibility the central lever.
• Use when: The subject is difficult, harmful, or unnecessary to relocate, but the rear boundary is legally, financially, technically, or politically adjustable; Releasing the rear boundary preserves more continuity and value than moving the entire subject.
• Typical domains: coastal land use, infrastructure, organizational governance, network architecture
• Common mechanisms: setback requirement, rolling easement or boundary policy, phased buyout or transfer program

Subject-Relocation Retreat · subtype · recognized

Moves the exposed subject, its essential state, or its successor function into a prepared receiving zone when the rear boundary cannot be released.

• Distinct from parent: This variant makes destination fit, state transfer, transition support, and loss during movement especially load-bearing.
• Use when: The advancing front and fixed rear boundary cannot be modified enough to preserve viability in place; A receiving zone can sustain the subject and the move can begin before the corridor closes.
• Typical domains: infrastructure, ecology, information systems, public services
• Common mechanisms: migration wave plan, migration readiness assessment, transition support plan, assisted migration or translocation plan

Rolling Retreat Corridor · temporal variant · recognized

Maintains a connected band of usable space that shifts over time so gradual movement can continue as the pressure front advances.

• Distinct from parent: The parent can use a one-time destination and route; this variant requires recurrent corridor renewal and front-relative boundary management.
• Use when: The subject migrates or is transferred incrementally rather than in one discrete move; Continuity depends on preserving connected intermediate states, not only a final destination.
• Typical domains: coastal habitat, climate adaptation, logistics, service migration
• Common mechanisms: rolling easement or boundary policy, controlled corridor, receiving zone reservation, closure horizon dashboard

Staged Functional Withdrawal · implementation variant · recognized

Withdraws functions, dependencies, or assets in an ordered sequence while preserving essential service until the successor configuration is stable.

• Distinct from parent: This variant emphasizes sequencing, parallel operation, dependency transfer, and cutoff criteria.
• Use when: The subject is a coupled system that cannot be moved intact; Different functions have different lead times, mobility, criticality, and salvage value.
• Typical domains: infrastructure, software, organizational operations, public services
• Common mechanisms: migration wave plan, parallel site or system run, decommissioning and restoration runbook

Near names: Adaptive Retreat Planning, Preemptive Relocation, Closure-Horizon Retreat, Retreat Corridor Design, Squeeze-Relief Planning.