ArcGIS Desktop, including ArcMap, retired on March 1, 2026. If your survey team still relies on ArcMap 10.8.2, the next step is to validate a supported office and field-data workflow—not to look for an unofficial download or assume that every existing project will transfer unchanged.
This guide is for survey and GIS teams reviewing migration and GNSS data handover. TOKNAV supplies positioning and field equipment; we do not distribute ArcGIS installers, activation codes or cracked software.
What changed after ArcMap retirement?
Esri confirms the retirement in its ArcMap retirement announcement and ArcMap product life-cycle page. Retirement is a support milestone; it does not mean that every ArcGIS product or service has retired.
Esri distinguishes perpetual and subscription licenses. A valid perpetual license may continue to run the retired software, while subscription access depends on the subscription term. Confirm your organization’s entitlement and support position directly with Esri or its authorized representative. Do not assume that ArcGIS Pro is automatically free for every ArcMap user.
A migration checklist for survey teams
- Inventory the office workflow. List map documents, geodatabases, coordinate transformations, styles, reports, extensions, scripts and custom tools. Assign an owner to each business-critical deliverable.
- Check software and licensing. Review supported ArcGIS Pro versions, workstation requirements and organizational licensing with Esri. Keep installation and entitlement questions separate from the selection of field equipment.
- Test representative projects. Use copies of real project data, not the only production copy. Check imported maps, layers, symbology, labels and processing outputs rather than assuming that opening a document proves a successful migration.
- Review automation. Identify legacy Python scripts, add-ins and integrations. Validate each in the target environment and update it where required before replacing the production workflow.
- Validate field-data handover. Confirm file formats, coordinate system, units, height reference, feature schema and required positioning-quality fields. Test a small dataset from collection to the final office deliverable.
- Agree acceptance and rollout. Document comparison results, unresolved differences, backup arrangements and staff training. Move production work only after the responsible team accepts the test results.
Where GNSS field collection fits
Changing office GIS software does not automatically improve a field coordinate. The receiver, correction service, control checks and collection settings still need to be managed as one workflow.
Start with TOKNAV GNSS receiver options when the task requires survey positioning, or review the rugged GIS field-collection range for mapping workflows. Confirm supported interfaces and output formats for the exact model and collection application before ordering.
For projects using network corrections, our CORS/VRS solution overview provides the correction-path context. The controlled GIS field-data collection guide explains how to preserve coordinate and quality information through handover.
Field-to-office acceptance checks
- Coordinate-system identifiers and transformations are documented, including the vertical reference and geoid model where used.
- A known control point is checked in the field and after import into the target office project.
- Feature types, required attributes, units and identifiers survive export and import.
- Quality information such as solution type and observation time is retained where the workflow provides it.
- The final map, report or exported dataset is reviewed against the agreed project requirements.
A visually plausible map is not sufficient evidence of a correct transformation. Keep the raw field records and comparison results so that differences can be investigated.
Frequently asked questions
Is this an ArcGIS 10.8.2 download page?
No. Obtain software and licensing information through official Esri channels. This page covers migration planning and survey-data collection.
Does ArcMap retirement mean all ArcGIS software has ended?
No. The retirement applies to ArcGIS Desktop products described by Esri. Check the life cycle of the specific product and version your organization uses.
Can a TOKNAV receiver be chosen only because a team uses ArcGIS Pro?
No. Selection should be based on the field task, accuracy requirements, correction availability, collection application and validated handover formats. Software compatibility must be checked for the actual workflow.
What should we send TOKNAV before a field-equipment consultation?
Share your country, task, required positioning accuracy, correction method, collection application and intended output format. Do not send passwords, license keys or confidential project files.
Review your GNSS-to-GIS workflow
For positioning and field-collection equipment, request a GNSS field-data workflow review. For ArcGIS licensing, installer access and software support, contact Esri directly.