Plan a migration to a new framework or version for Logistics & Supply Chain

You are a senior engineer who has led large migrations, working with shippers, carriers and warehouse teams at a logistics company running warehouses and a delivery fleet.

## Goal
Plan a low-risk migration from the current framework or version to a new one.

## What matters in Logistics & Supply Chain
- Rules and standards that usually apply: driver working-hours limits; road safety and vehicle fitness; customs and trade paperwork (HS codes, e-way bills and GST in India); dangerous-goods rules; insurance and liability terms in contracts.
- Common risks to plan for: missed delivery windows; fuel price swings; damage and theft; customs holds; driver shortages.
- Tools commonly used: WMS; TMS; GPS fleet tracking; ERP; Excel.
- Words people in this field use: OTIF; last mile; 3PL; cross-docking; POD; bill of lading; FTL/LTL; reverse logistics.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- From: [CURRENT FRAMEWORK AND VERSION]
- To: [TARGET FRAMEWORK AND VERSION]
- App size: [e.g. 40 routes, 120 components, 300 tests]
- Release constraints: [e.g. no downtime, weekly releases]

## What to do
1. List the breaking changes and deprecated features that affect this app.
2. Choose a strategy: big bang, incremental, or strangler pattern, and explain why.
3. Break the migration into phases that each ship to production.
4. Define how you will test each phase and how to roll back.
5. Estimate effort and list the risks.

## What to deliver
- A phased migration plan with tasks
- A risk register with mitigations
- A testing and rollback checklist

## Rules
- Keep delivery windows, customs rules and driver-hours limits in mind throughout, and point out anything in my plan that would break them.
- Where it fits, connect your recommendations to on-time delivery rate and cost per shipment.
- Use plain language and short sentences. Use headings and tables where they make the answer easier to scan.
- Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- It is written for a logistics company running warehouses and a delivery fleet; nothing in it would read the same for any other business.
- Every item under "What to deliver" is included.