BIM 360 remains an earlier Autodesk platform for existing projects
Autodesk defines BIM 360 as a cloud-based construction-management platform connecting project, design, and construction teams. Its next-generation environment combined account and project administration with Document Management, Design Collaboration, Model Coordination, Field Management, Project Management, Cost Management, Insight, and mobile access. The name also covered Classic products with different architectures and lifecycles, so “BIM 360” is not one interchangeable application or entitlement.
New-project strategy now points to Autodesk Forma
Autodesk says there are currently no plans to retire the BIM 360 next-generation platform, but no new features will be added and new projects should begin on Autodesk Forma. Forma is the current name for the environment previously branded Autodesk Construction Cloud, or ACC. It is a separate platform, and Autodesk says an existing BIM 360 project cannot be automatically converted into the newer platform interface.
BIM 360 Docs provides the controlled project-document layer
Document Management—commonly searched as BIM 360 Docs—organizes Plans and Project Files with folders, permissions, versions, viewing, comparison, markups, issues, RFIs, and approval reviews. In a disciplined common data environment, document managers publish controlled information while project members review the right version and leave traceable comments or issues. Autodesk’s Document Management workflow also supports offline mobile work followed by synchronization. Folder permissions, naming rules, approval responsibilities, and archival procedures still require project governance; cloud storage does not create control by itself.
Design and model coordination depend on the module and entitlement
Design Collaboration uses team spaces, packages, timelines, and changes to coordinate design information across companies. Model Coordination aggregates models, checks clashes, supports review, and turns coordination findings into issues. Its handoffs with Revit and Navisworks matter when authoring, federation, clash review, and issue resolution cross application boundaries. Buyers should verify which services are active in the account and which desktop subscriptions provide the required authoring or coordination entitlement.
Field, Project Management, and Insight serve different operational roles
Field Management captures site communication through issues, checklists, and daily logs. Project Management structures RFI and submittal workflows, including manager and reviewer responsibilities. Insight assembles dashboards and analytics for design, quality, safety, project controls, cost, and reports, subject to module access and role permissions. These services can share project context, but reliable reporting still depends on consistent issue classification, accountable assignees, current due dates, and teams actually completing the source workflows.
Admin is where access, projects, companies, and services are governed
Account Admin controls account-level details, projects, companies, members, and available services; Project Admin handles project profiles, members, companies, and module access. Autodesk’s administration guidance distinguishes unified next-generation membership from Classic product administration. Permissions should follow project roles and contractual responsibilities, with named owners for account activation, offboarding, reviews, and exports. Regional accounts also matter: US and European projects use different sign-in endpoints, and Autodesk does not offer an automatic transfer between those data centers.
Login and download searches describe several different tasks
BIM 360 is primarily browser-based, so there is no universal desktop “BIM 360 software” installer. Members sign in with an Autodesk ID through the correct regional Admin or Docs endpoint; Autodesk documents separate US and European login routes. Downloads may instead mean exporting project files, installing a mobile app, or installing Desktop Connector to expose Document Management files through a connected local drive. Autodesk recommends current 64-bit versions of Chrome, Firefox, Safari, or Edge for the browser service; mobile and connector requirements should be checked against the latest support pages before deployment.
Pricing is contract- and product-specific rather than a public BIM 360 list price
A blank annual price is not useful, but replacing it with an invented number would be worse. Existing BIM 360 access depends on the account’s subscriptions and legacy entitlements. Current buyers are directed to Autodesk Forma products and bundles, where Autodesk publishes quote-led pricing with user-, project-, and account-based options. Autodesk also advertises 30-day trials for selected current Forma products; that does not establish a new, universal BIM 360 trial. Confirm the exact module, seat model, region, contract term, storage arrangement, support plan, and migration scope with Autodesk or an authorized partner.
BIM 360 Glue requires immediate transition action
BIM 360 Glue is a Classic coordination product, not a synonym for the whole BIM 360 platform. Autodesk’s Glue end-of-life FAQ sets July 31, 2026 as the discontinuation date and says existing data will not be accessible afterward. The recommended replacement is Model Coordination in Autodesk Forma. Glue customers can use the in-product Data Transition tool to copy model data into the Files tool, then archive it or create a coordination space. Before cutoff, teams should inventory models, export required history, test downstream integrations, validate permissions, and confirm how Navisworks or Point Layout access is licensed after Glue entitlements end.
Keep BIM 360 for controlled closeout; choose the current platform for new work
BIM 360 remains suitable when an active project, contract, data location, integration, or delivery plan depends on its next-generation services. Autodesk recommends finishing those projects in their existing interface rather than expecting automatic migration. For a new program, compare Forma products against the required document, coordination, field, cost, and analytics workflows. The decision is whether the team can govern the existing environment through completion or should establish new standards, templates, integrations, and training on Autodesk’s current platform.
