Straight-to-8 jump pattern
Parent: MongoDB Upgrade Paths · Published reference · snapshot 2026-10-23 · skill mongodb-cohort-b7cbe85f979c
↓ Facts as markdownall context files
Source-anchored research for Straight-to-8 jump pattern. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Comparisons and alternatives
- Mongosync 1.20's compatibility matrix permits 6.0-to-8.0 and 7.0-to-8.0, but lists 5.0-to-7.0 rather than 5.0-to-8.0. Direct-to-8 support must therefore be checked for the exact source version. (low confidence) (verified as of 2026-10-23) [source]
Facts and statements
- An in-place upgrade from MongoDB 6.0 to 8.0 must pass through 7.0. MongoDB documents this sequence explicitly; Percona Operator requires a separate upgrade for each major version, and IBM Cloud permits only the next major version. (high confidence) (verified as of 2026-10-23) [source]
- Before replacing MongoDB 7.0 binaries with 8.0 binaries, the documented standalone procedure requires featureCompatibilityVersion to be 7.0. Reaching intermediate binaries while retaining FCV 6.0 does not satisfy that prerequisite. (low confidence) (verified as of 2026-10-23) [source]
- For in-place planning, interpreting “Straight-to-8” as one project containing sequential supported upgrades is consistent with the documented procedures. Interpreting it as permission to replace a 6.0 server directly with 8.0 is inconsistent with them. This is a synthesis of the procedures, not an established vendor definition of the phrase. (medium confidence) [source]
- Upgrade planning must check target-version driver compatibility and test application behavior in a staging deployment; reaching the desired server version alone does not establish application compatibility. (high confidence) [source]
- Cross-cluster synchronization offers a direct 6.0-to-8.0 migration into a separate destination. MongoDB Mongosync 1.20 lists that source/destination pair, and Percona documented support for the same pair in ClusterSync 0.9.0 on June 4, 2026. This does not authorize skipping 7.0 during an in-place binary upgrade. (high confidence) (verified as of 2026-06-04) [source]
- Mongosync 1.20 does not list 5.0-to-8.0 as a supported pair: its matrix permits 5.0-to-7.0 and 6.0-to-8.0. The documented minimum patches for a 6.0-to-8.0 sync are 6.0.24 and 8.0.5, with FCV 6.0 and 8.0 respectively. The versioned documentation has no visible publication date; the date here records the source snapshot. (low confidence) (verified as of 2026-10-23) [source]
- Percona’s August 5, 2024 backup-and-restore experiment skips from 3.6 to 7.0, but explicitly says skipping versions with backups is not recommended. It is an experiment with support and data-compatibility caveats, not evidence of a generally supported direct-to-8 upgrade path. (low confidence) (verified as of 2024-08-05) [source]
- The September 23, 2026 5e-srd-api issue proposes changing a mongo:6.0.28 image to mongo:8.0 and checking configuration, driver support, image builds, data refresh, and integration tests. It does not demonstrate a supported upgrade of an existing 6.0 data directory to 8.0. (low confidence) (verified as of 2026-09-23) [source]
- Mongosync 1.20 requires at least MongoDB 6.0.24 with FCV 6.0 for a 6.0 source, and at least MongoDB 8.0.5 with FCV 8.0 for an 8.0 destination. (low confidence) (verified as of 2026-10-23) [source]
- Percona's June 4, 2026 account says ClusterSync 0.9.0 tests 6.0-to-8.0 migration on replica-set and sharded topologies; its version gate compares major versions and rejects downgrades, without enforcing minimum patch versions. (low confidence) (verified as of 2026-06-04) [source]
- Treat generic dump/restore across distant major releases as a separate, unproven path: MongoDB documents restoring to the same major version or FCV, and Percona's 2024 multi-major backup experiment warns against interpreting an apparently successful restore as proof of data compatibility. (medium confidence) [source]
- IBM Cloud's June 26, 2026 upgrade guide limits in-place upgrades to the next major version and documents backup restoration into a new deployment as another path; its displayed upgrade-path table lists MongoDB 7 to MongoDB 8, so it does not establish an arbitrary direct-to-8 restore path. (low confidence) (verified as of 2026-06-26) [source]
Children
- No children recorded.