Strangler fig migration in 30 seconds: route, own data, cut over
Silent video: no voiceover, music or sound effects. This transcript repeats every on-screen word and describes each scene.
The film includes the topic label "Strangler fig migration", the note "Illustrative diagram", the TecnoStack logo and progress numbers 1, 2, 3, 4, 5, 6. Elements enter and leave during transitions; in portrait, the closing sign-off replaces the footer.

[0:00–0:05] Beat 1 of 6 (intro)
Kicker: Strangler fig migration
Headline: Replace one capability at a time
Support: Plan each transition
Diagram (decision paths): Legacy system; One big rewrite; Capability by capability
Connections: Legacy system → One big rewrite; Legacy system → Capability by capability
Highlighted: Capability by capability
Scene: Branching diagram: Legacy system, One big rewrite, Capability by capability. Connections: Legacy system to One big rewrite; Legacy system to Capability by capability. Emphasis: Capability by capability.

[0:05–0:10] Beat 2 of 6 (step1)
Kicker: 01
Headline: Route capability by capability
Support: Preserve a clear ownership boundary
Diagram (hub and spokes): Routing layer; Callers; Legacy system; New loyalty service
Connections: Callers → Routing layer; Routing layer → Legacy system; Routing layer → New loyalty service
Highlighted: Routing layer
Scene: Network: Routing layer, Callers, Legacy system, New loyalty service. Connections: Callers to Routing layer; Routing layer to Legacy system; Routing layer to New loyalty service. Emphasis: Routing layer.

[0:10–0:15] Beat 3 of 6 (step2)
Kicker: 02
Headline: One authoritative writer
Support: Transfer ownership after reconciliation
Diagram (timeline): Legacy owns writes; Transfer ownership; Retire sync
Connections: Legacy owns writes → Transfer ownership; Transfer ownership → Retire sync
Highlighted: Transfer ownership
Scene: Sequence: Legacy owns writes, Transfer ownership, Retire sync. Connections: Legacy owns writes to Transfer ownership; Transfer ownership to Retire sync. Emphasis: Transfer ownership.

[0:15–0:20] Beat 4 of 6 (step3)
Kicker: 03
Headline: Shadow without side effects
Support: Then move reads and ownership
Diagram (flow): Compare outputs; Move reads; Move writes; Retire after checks
Connections: Compare outputs → Move reads; Move reads → Move writes; Move writes → Retire after checks
Highlighted: Move writes
Scene: Flow: Compare outputs, Move reads, Move writes, Retire after checks. Connections: Compare outputs to Move reads; Move reads to Move writes; Move writes to Retire after checks. Emphasis: Move writes.

[0:20–0:25] Beat 5 of 6 (step4)
Kicker: 04
Headline: Plan recovery before cutover
Support: Reconcile data before switching routes
Diagram (flow): Pause new writes; Reconcile data; Restore old ownership
Connections: Pause new writes → Reconcile data; Reconcile data → Restore old ownership
Highlighted: Reconcile data
Scene: Flow: Pause new writes, Reconcile data, Restore old ownership. Connections: Pause new writes to Reconcile data; Reconcile data to Restore old ownership. Emphasis: Reconcile data.

[0:25–0:30] Beat 6 of 6 (close)
Kicker: TECNOSTACK
Headline: Track every retirement
Support: Finish the migration deliberately
Diagram (evidence checklist): Modernization map; Exit criteria per slice; Retirements tracked; Architecture review
Highlighted: Retirements tracked
Sign-off: TecnoStack logo and tecnostack.com
Scene: Comparison without scores: Modernization map, Exit criteria per slice, Retirements tracked, Architecture review. Emphasis: Retirements tracked.