Unity 6.0 LTS Support Ends October 2026 - Indie Migrate Worksheet

If you searched unity 6.0 lts support ends in October 2026, you do not need another Hub screenshot of a shiny Supported patch. You need a fill-in migrate worksheet that locks four decisions before Discord invents a panic upgrade:

1. Support cliff — Unity 6.0 LTS is supported through October 2026 (Unity 6 release support)
2. Destination lane — 6.3 LTS (supported until December 2027) or a current Supported Update line for mid-cycle work
3. Package + platform matrix — what breaks if you leave 6.0 this month
4. Ship-branch governance — clone first; never “just try Hub’s recommended” on the store-facing AppID during fest week

This URL is that worksheet. It is not the Stop Upgrading Unity Mid Steam Next Fest Week opinion (pin the live demo; refuse Hub FOMO through Oct 26). It is not the Unity 6.6 LTS upgrade safety sprint (calm one-week migration playbook after you already chose a destination). It is not the Unity 6.5 BIRP deprecation playbook (render-pipeline keep/hold). Those URLs own refusal, sprint steps, and BIRP. This URL owns October 2026 support-end planning — cite-worthy tables outsiders can footnote when diligence asks “are you still on an unsupported LTS?”

Why this matters now

October is the month Unity’s own support page draws a hard line under 6.0 LTS. Per Unity 6 release support, Unity 6.3 LTS is supported until December 2027, while Unity 6.0 LTS is supported through October 2026. Enterprise and Industry subscribers get an extra year on LTS lanes — but most micro-studios are on standard two-year LTS math. That does not mean projects stop opening on November 1. It means fresh bug fixes, critical platform updates, and “we are on a supported editor” diligence language stop being free for standard 6.0 LTS seats.

Meanwhile Steam Next Fest: October 2026 still runs October 19–26. Hub will keep offering Supported patches. Teams that confuse support cliff with mid-fest FOMO either freeze forever on 6.0 folklore or smash a live demo branch with an untested Update install. Both are governance fails.

Direct answer: Fill this worksheet this month. Decide MIGRATE_6_3_LTS, MIGRATE_UPDATE, or DOCUMENT_STAY (with dates and owner). Clone before you open Hub. If a demo is live or about to go live, pin first (mid-fest pin opinion), then schedule the migrate sprint after branch unset using the 6.6 safety sprint pattern — even when your destination is 6.3 LTS, not 6.6.

Who fills this worksheet

Time: 45–60 minutes first pass; 15 minutes to update after each clone green build.
Honest limit: Unity can revise support language; re-check unity.com/releases/unity-6/support before you quote dates to a partner. Support end ≠ binary “editor deletes itself.” This worksheet models published October 2026 support math — it does not replace your license terms or Enterprise entitlements.

Non-repetition

Pair engine ops with the Unity guide hub, 18 free Unity 6.6 migration regression triage resources, and Unity 6.6 LTS asset import worker hangs fix when the first clone import fails.

Unity rules you must quote (not invent)

From Unity 6 release support and the Unity 6.3 LTS announcement:

1. LTS — released about once a year; two years of support; extra year for Unity Enterprise and Unity Industry.
2. Unity 6.3 LTS is supported until December 2027 (standard two-year window from its LTS positioning).
3. Unity 6.0 LTS is supported through October 2026.
4. Supported Update releases — multiple per year; supported until the next Update publishes; same QA bar as LTS for production readiness; preferred for new and mid-cycle productions that want newest platform work.
5. LTS is recommended for live-service games and creators about to lock production on a specific editor version.
6. Alpha/beta are open in Hub — not for production ship branches; back up before opening.
7. Update releases are not old Tech Streams — they are production-ready with LTS-class critical fixes until superseded.

Pasteable diligence line:

We are leaving Unity 6.0 LTS because standard support ends October 2026. Destination is 6.3 LTS (lock through Dec 2027) or a named Supported Update with a written re-eval date. Clone-first; ship branch pinned until green receipt.

Beginner path — 50 minutes

Prerequisites: Unity Hub installed; project backed up (git tag or zip); you know whether a Steam demo is live this week.

1. Open Unity 6 support and write today’s date next to the 6.0 / 6.3 sentences.
2. Fill Section A (identity) and Section B (lane choice).
3. If Next Fest demo is live or opens within 7 days → choose PIN_THEN_MIGRATE and stop Hub installs on the demo machine (pin opinion).
4. Otherwise clone the project → install destination editor → open clone only.
5. Fill Section C packages and Section D regression gates.
6. Paste the Discord script. Save the receipt JSON shape.

Common beginner mistakes:

Section A — Project identity (fill in)

Section B — Lane choice (pick exactly one)

Unity’s support page separates LTS lock from Supported Update mid-cycle. Fill the decision — do not leave “we’ll see.”

Destination worksheet

Worked examples (patterns, not fake case studies)

Pattern Soft-lock Steam PC — choose MIGRATE_6_3_LTS
You ship in Q1 2027, no console cert this quarter, BIRP already decided. Destination 6.3 LTS. Run clone import + Input System smoke + Addressables build. Do not chase 6.6 features until post-launch.

Pattern Mid-cycle mobile + new XR package — choose MIGRATE_UPDATE
You need platform packages that only land on Supported Updates. Write the exact Update string and a 30-day re-eval. Still clone-first. Pair Android GLES floor checks with the queued device-matrix thinking (do not invent device claims — measure).

Pattern Next Fest week — choose PIN_THEN_MIGRATE
Demo opens Oct 19. Pin 6.0 or last-green 6.3 on the demo AppID. Schedule migrate sprint for the week after branch unset. Refusal script lives on the mid-fest pin URL.

Pattern Enterprise on 6.0 with extra year — DOCUMENT_STAY possible
Write the entitlement end date, the partner who approved stay, and the quarter you will still migrate. “Enterprise buys time” is not “never migrate.”

Section C — Package and plugin cliffs

List every package that has historically broken upgrades. Empty cells are a fail.

BIRP note: If you are still on Built-In and considering a jump that lands on 6.5+ deprecation language, read the 6.5 BIRP playbook as a sibling — do not merge that night into this support-end worksheet. Support cliff and render-pipeline cliff are different clocks.

Section D — Regression gates (must all PASS before ship merge)

If G1 fails, stop. Use import worker hang help patterns even when the destination is 6.3 — import hangs are version-family cousins.

Section E — Calendar (October → post-fest)

CapEx four-liner (companies)

1. Risk of stay: Standard 6.0 LTS support ends October 2026 — platform patches and diligence language degrade.
2. Destination cost: One clone week + package owner hours + optional console re-cert if SDKs move.
3. Avoided cost: Mid-fest demo crash / refund spike from untested Hub install.
4. Decision: MIGRATE_6_3_LTS / MIGRATE_UPDATE / PIN_THEN_MIGRATE / DOCUMENT_STAY — owner + date above.

Discord paste (creators)

Unity 6.0 LTS support ends October 2026 (unity.com/releases/unity-6/support).
We are NOT installing Hub’s “recommended” on the ship branch this week.
Decision: [6.3 LTS | named Update | pin then migrate].
Clone first. Gates G1–G8 before merge. Receipt in #eng.

Developer path — clone sprint (after lane choice)

Use this when Section B is **MIGRATE_*** and you are not in PIN fire.

Day 0 — Inventory

1. Tag pre-migrate-6-0-YYYYMMDD on the ship branch.
2. Record Hub installs present on every machine that can push builds.
3. Export Package Manager list (or Packages/manifest.json + lock).
4. Write destination editor string in Section B — no “latest.”

Day 1 — Disposable clone

1. Clone to a new folder or branch migrate/6-3-lts (or migrate/update-XXXX).
2. Install destination editor via Hub Archive if needed — do not assume “Install” equals your string.
3. Open clone only. Let import finish. If hang → help article; do not “force” ship branch.
4. Fix compile errors in a single PR stack on the migrate branch.

Day 2 — Player and content

1. Build Development Player; boot to menu.
2. Build Release Player; size sanity check.
3. Run Addressables/content build if used.
4. Fill G2–G5.

Day 3 — Platform and CI

1. Deck/mobile smoke if in scope.
2. Point CI at destination editor image; rebuild green.
3. Fill G6–G7.
4. Only then plan ship-branch merge + Steam build_id update (G8).

Honest limits for developers

• 6.3 LTS ≠ feature freeze forever — it is a support harbour, not a vow to ignore security advisories.
• Update lane ≠ reckless — it is a written re-eval commitment.
• Safety sprint URL still applies for sequencing even when destination is 6.3 — do not invent a second migration religion.
• OpenGLES / Android floors on newer 6.x lines are separate measurement work — do not copy rumor matrices into this receipt.

Failure modes (and what to write)

Receipt JSON shape

{
  "receipt_type": "unity_6_0_lts_support_end_migrate_v1",
  "filled_at": "2026-10-11",
  "product": "",
  "current_editor": "6000.0.xxf1",
  "decision": "MIGRATE_6_3_LTS",
  "destination_editor": "6000.3.xxf1",
  "pin_until": null,
  "gates": {
    "G1_editor_open": false,
    "G2_player_build": false,
    "G3_input": false,
    "G4_content": false,
    "G5_scene_smoke": false,
    "G6_platform": false,
    "G7_ci_match": false,
    "G8_store_claim": false
  },
  "owners": {
    "decision": "",
    "clone": "",
    "ci": ""
  },
  "support_sources": [
    "https://unity.com/releases/unity-6/support",
    "https://unity.com/blog/unity-6-3-lts-is-now-available"
  ],
  "notes": ""
}

Save beside your BUILD_RECEIPT. Diligence prefers a boring JSON over a Slack vibe.

Monday checklist (creators + leads)

1. Quote the support page dates in #eng — not a YouTuber.
2. Fill Section A–B in one sitting.
3. If fest demo risk → pin; link the pin opinion.
4. Else open clone only.
5. Assign package owners from Section C.
6. Do not merge until G1–G8 pass.
7. Paste Discord script when someone shares a Hub screenshot.
8. Update CapEx four-liner for the next partner email.

Relationship to mid-fest pin and safety sprint

Think of three layers:

1. Governance refusal (fest week) — Stop mid-fest upgrade
2. Support-end decision (this URL) — choose lane + fill cliffs
3. Execution sprint — 6.6 safety sprint sequencing on the clone

Skipping layer 2 is how teams pin forever and still fail diligence in November. Skipping layer 1 is how teams migrate on the live depot. Skipping layer 3 is how teams “decide 6.3” and never green a player build.

Enterprise and Industry note

Unity’s support page states an additional year of LTS support for Enterprise and Industry. If that applies:

• Write the entitlement end date in Section A.
• DOCUMENT_STAY is allowed only with that date + named approver.
• Still schedule MIGRATE_6_3_LTS before entitlement end — extra year is a runway, not a destination.

FAQ

Does Unity 6.0 LTS stop working on November 1, 2026?

No. Support end means the standard support commitment for fixes and critical platform updates ends for that LTS window — not that the editor binary vanishes. Treat it as a risk and diligence cliff.

Should every indie jump to Unity 6.6 because Hub recommends it?

No. For support-end planning, 6.3 LTS is the usual harbour through December 2027. Update lanes are for mid-cycle needs with a written re-eval. Mid-fest installs on ship branches remain a refuse — see the pin opinion.

Is a Supported Update “less stable” than LTS?

Unity states Update releases get the same QA testing and production-ready posture as LTS, with support until the next Update. Your risk is cadence and re-validation, not a secret beta label.

Can we stay on 6.0 if we ship next week?

Possibly under DOCUMENT_STAY with partner-visible risk language — especially if Enterprise entitlement still covers you. Still write the post-ship migrate quarter. Soft-lock is not “forever 6.0.”

How is this different from the 6.5 BIRP playbook?

BIRP deprecation is a render-pipeline clock. This worksheet is a support-end clock. You may need both nights; do not merge keywords.

What if our clone fails G1 for days?

Stay pinned. Do not merge red. Use import hang help, package bisect, and the safety sprint’s “stop rules.” Support cliff pressure never justifies a red ship branch.

Do we need console re-cert if we migrate?

If console SDKs or certified editor strings move, yes — budget it in CapEx. If you are PC/Deck only this quarter, say so explicitly in Section A.

Where do Android OpenGL ES floors fit?

On newer 6.x lines, graphics minimums can change. Measure devices; do not paste rumors. A dedicated GLES matrix article may sit in the backlog — this worksheet only forces you to name platforms and pass G6.

Key takeaways

1. Unity 6.0 LTS is supported through October 2026 — fill a migrate worksheet this month.
2. Prefer 6.3 LTS for lock-in harbour through December 2027, or a named Update with re-eval.
3. Support end ≠ editor deletion — it is patches + diligence language.
4. Clone first; never Hub-upgrade the live demo AppID during fest week.
5. Fill package cliffs (Section C) and G1–G8 before merge.
6. CapEx four-liner + receipt JSON beat Slack folklore.
7. Mid-fest pin, this worksheet, and the safety sprint are three layers — use all three.
8. Enterprise extra year buys runway, not a forever stay.
9. Re-check Unity’s support page before partner quotes.
10. Discord paste exists so Hub screenshots do not set policy.

Related reading

• Stop Upgrading Unity Mid Steam Next Fest Week - Pin 6.3 LTS 2026 — fest-week refusal
• Unity 6.6 LTS Upgrade Safety Sprint - Migration Playbook for Small Teams 2026 — execution after lane choice
• Unity 6.5 Upgrade - BIRP Deprecation Playbook for Indies 2026 — pipeline cliff sibling
• Unity 6.3 LTS Patch Notes Explained for Indie Teams
• Unity 6.6 LTS Stabilization Wave - Revalidation Checklist
• 18 Free Unity 6.6 Migration Regression Triage Resources
• Unity Guide
• Unity 6.6 LTS Asset Import Worker Hangs - First Import Fix
• Unity 6.4 Upgrade Broke Input Actions - Wrapper Fix

Cite Unity 6 release support and Unity 6.3 LTS is now available next to every support-date claim — then still fill the worksheet instead of vibes-upgrading Hub.