How to Migrate from ArcGIS Field Maps to Atlas: A Practical Guide

Migrating off ArcGIS Field Maps is usually less painful than teams expect. Most of the work is exporting your existing data, rebuilding forms in the new tool, and running a parallel pilot to prove the switch. If you're moving to Atlas because of cost, ease of use, or the desire to escape the ArcGIS license dance, here's a practical playbook to make the transition smooth.

Why Teams Migrate

Common reasons for leaving Field Maps:

Cost climbs with ArcGIS user types and storage
ArcGIS dependency means you can't simplify the stack
Onboarding friction for non-technical field staff
App store dependencies for iOS and Android
Office and field tools live in separate apps

If any of these are blocking your team, a migration is worth doing well.

Step 1: Inventory What's Live

Before touching anything, document what you have:

Forms currently deployed (and their versions)
Feature services backing those forms
Maps referenced by Field Maps users
Offline areas crews depend on
Integrations with downstream systems (work orders, asset management)
User accounts and roles

This inventory becomes your migration checklist.

Step 2: Export Your Data

Pull your data out of ArcGIS into open formats:

Feature services export to Shapefile, GeoJSON, or File Geodatabase
Attachments and photos export through the REST API or ArcGIS Pro
Web maps can be recreated in Atlas from the same underlying layers
User lists export for re-invitation

GeoJSON is the smoothest import format for Atlas.

Step 3: Rebuild Forms in Atlas

Atlas's form builder is drag-and-drop, so rebuilding existing forms is fast:

Open the form builder
Add fields that match your existing schema
Configure conditional logic
Mark required fields
Add photo and signature fields as needed
Test the form on a phone

Most teams rebuild a form in 30 minutes or less.

Also read: Complete Guide to Building Field Data Collection Apps with Maps

Step 4: Import Your Layers

Bring your exported data into Atlas:

Drag and drop GeoJSON or Shapefile into a new map
Style layers to match the original look
Set up labels and popups as needed
Configure permissions for the team

The result should look familiar to anyone who used the old maps.

Step 5: Configure Offline Areas

If crews rely on offline use:

Pre-cache the work areas they need
Test on a real device with airplane mode
Document any sync checkpoints (lunch, end of day)

Also read: Offline Field App: How to Collect Data Without Internet

Step 6: Run a Parallel Pilot

Don't cut over cold. Run both tools for one inspection cycle:

Pick one team and one workflow
Run both Field Maps and Atlas in parallel for two weeks
Compare data quality, cycle time, and team feedback
Iterate the Atlas setup based on what you learn

A successful parallel pilot is the proof you need to switch the whole team.

Step 7: Train and Communicate

Atlas trains faster than Field Maps for most users, but communicate the change clearly:

What's changing: new tool, new link, new form
What's staying the same: data, workflow, expectations
How to access: just a link—no app store
Where to get help: documentation and contact paths

Most teams need 30 minutes of training per crew, not a multi-day rollout.

Step 8: Cut Over and Decommission

Once the pilot is solid:

Switch the whole team on a defined date
Keep Field Maps available for 30 days as a backup
Migrate historical data to Atlas so the team works from one system
Decommission Field Maps licensing at the next renewal

Also read: How to Choose a Field App: A Buyer's Checklist for Operations Teams

Common Migration Pitfalls

Migrating mid-season—pick a slow stretch in your workflow
Trying to redesign forms during migration—rebuild first, redesign later
Skipping the parallel pilot—you'll surface issues too late
Underestimating photo migration—budget time for it
Forgetting downstream integrations—connect them before cutover

What Stays in ArcGIS

Some teams keep ArcGIS for specific needs—heavy analysis, regulatory deliverables, or existing integrations. Atlas plays well alongside ArcGIS:

Export Atlas data to GeoJSON or Shapefile for ArcGIS Pro
Use ArcGIS for deep analysis when needed
Use Atlas for field collection, dashboards, and shared maps

A migration doesn't have to mean abandoning ArcGIS—it can mean offloading the parts Atlas does better.

Make the Switch With Atlas

Atlas is the most common Field Maps replacement because the migration is straightforward and the day-to-day is simpler. Browser-based, offline-capable, and built for non-technical users.

What Atlas Gives You

You can:

Rebuild your existing forms in minutes
Import GeoJSON, Shapefile, or CSV with drag and drop
Pre-cache work areas for offline use on any device
See submissions appear on shared maps and dashboards in real time