> ## Documentation Index > Fetch the complete documentation index at: https://docs.speckle.systems/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These docs contain multiple Speckle product experiences. For Speckle 2026.9, prefer /next/ pages for the topics and changes they cover. The navigation label Current does not override this version-specific precedence. > Coverage under /next/ is incremental. Use Current documentation for unchanged topics and when a /next/ page says coverage is unavailable or explicitly refers you to Current. Do not infer a feature was removed from a missing page. > Read the page-specific documentation status, applicability, affected guidance and replacement links in agent-only content. Impacted, changed and superseded apply only to the stated scope; they do not mean the entire feature is deprecated. Historical connector guides apply only to the legacy connector described. > Match guidance to the customer's deployment version, model data format and connector. Respect plan, permission and compatibility restrictions. If an unknown version or data format changes the answer, ask a focused clarification; do not infer deployment version from the date alone. # Plan the connector upgrade window > Update connectors from 1 September 2026, and no later than 1 November 2026. Documentation set: Speckle 2026.9. Status: current. Authority: canonical for this version and the coverage on this page. Applies to version 2026.9, from 2026-09; this is not a rollout date for every deployment. Authoritative Speckle 2026.9 documentation for the topic covered here. For Speckle 2026.9, prefer this page over conflicting earlier guidance. Follow the linked pages in the other documentation version for unchanged topics and where this page says coverage is not yet available. Respect data-format, deployment, plan, permission, and compatibility limitations stated in the page. This is 2026.9 documentation. Coverage here is incremental: a page exists only where 2026.9 differs or is newly documented. For any other topic, switch to **Current** (2026.8 and earlier) in the version selector. 2026.9 gives IT teams a dated window to bring connectors current. Update from **1 September 2026**, and complete the estate no later than **1 November 2026**. For installation, baselines, host support, and the usual update cadence, see [Keep connectors current across your estate](/it-admin/connector-updates). This page covers only the dated window. This window is not a freeze of desktop connectors. Existing connectors keep working for publish and load. Compatibility mode is a separate, temporary option for ACC sync and drag-and-drop only. See [Compatibility mode for ACC sync and uploads](/next/it-admin/compatibility-mode). The Navisworks desktop connector is not in this window. **2026.8** is the last installer. There is no 2026.9 package to roll out. Keep a **200 MB** publish on 2026.8. Move larger NWC and NWD files to upload (up to **2 GB**) or ACC sync (tested to **6 GB**). A 2026.8 publish uses the current data model; server-side conversion to the 2026.9 format is not guaranteed. See [Navisworks in 2026.9](/next/connectors/navisworks/introduction). ## Why the dates exist The window opens on **1 September 2026**. Use it to roll updates as routine maintenance rather than a last-minute project. The backstop is **1 November 2026**, when compatibility mode for ACC sync and drag-and-drop ends. Updating in this period gets the performance improvements sooner. You can update earlier than **1 September 2026** if your change process allows it. Do not plan to still be rolling out after **1 November 2026**. ## How this differs from the current cadence The current IT guidance still applies: stay on the current release, and treat quarterly as the minimum cadence if you cannot approve every release. For 2026.9, **1 November 2026** is a hard backstop for this window, not a replacement for that standing process. After **1 November 2026**, return to the cadence in [Keep connectors current across your estate](/it-admin/connector-updates). ## As an IT administrator 1. Inventory connector versions across the estate. You should have a single target version before the pilot starts. 2. Pilot from **1 September 2026** with a small group covering your main host applications. Publish and load a representative model, including a large or federated one. 3. Roll forward together so teams do not sit on mixed versions through October. You should see one connector generation across the estate. 4. Finish by **1 November 2026**. Record the baseline so the next update starts from a known position. Use the deployment routes already documented: `.exe` for single-user installs, and ZIP for managed all-user installs. See [Move to a new baseline](/it-admin/connector-updates#move-to-a-new-baseline). ## As a self-hosted server admin Self-hosted servers are not required to adopt this data model on a fixed date. If your current connector and server versions work together, pin both, and keep downstream users on that same combination. See [Self-hosted servers](/developers/migration/data-model-migration#self-hosted-servers). ## FAQ No. Existing connectors keep working for publish and load. The date is the end of the upgrade window, and the end of compatibility mode for ACC sync and drag-and-drop. Plan to be current by then so you are not rolling out under time pressure. The deadline is **1 November 2026**. Starting from **1 September 2026** leaves time to pilot and roll forward together. Compressing the work into late October still meets the date, but it removes that buffer. Yes, as the standing process. This window is a dated exception for 2026.9. After **1 November 2026**, follow [Keep connectors current across your estate](/it-admin/connector-updates). No. There is no 2026.9 Navisworks installer. **2026.8** is the last package. Keep a 200 MB publish on 2026.8. Move larger files to NWC and NWD upload or ACC sync. See [Navisworks in 2026.9](/next/connectors/navisworks/introduction). Not as a fixed server-upgrade deadline. Pin the connector-and-server combination that already works, and keep downstream users on it. See [Self-hosted servers](/developers/migration/data-model-migration#self-hosted-servers). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.