---
schema_version: "1"
id: 6241db534f34dad1896d46986df464a994c4c3166b6a576ad3a283ad118730f1
title: Salesforce Maps Go-Live Checklist
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/salesforce_maps_setup_golive_checklist.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.salesforce_maps_setup_golive_checklist.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3cca5d9b56d4fc5b99e79d0463587dadd8b16b76f5c1fb76cfd960798fa76941
description: "Verify production readiness across five checklist categories: pre-launch readiness, testing and validation, training and documentation, change management, and ongoing maintenance."
products:
  - Sales
  - Salesforce Maps
release: "264"
---
# Salesforce Maps Go-Live Checklist

Verify production readiness across five checklist categories: pre-launch readiness, testing and validation, training and documentation, change management, and ongoing maintenance.

## Pre-Launch Readiness

Pre-Launch Readiness Checklist   
| Category | Item | Complete |
| --- | --- | --- |
| Installation | Salesforce Maps package installed in production | ☐ |
| Installation | Package version matches tested sandbox version | ☐ |
| Installation | Advanced add-on package installed if applicable | ☐ |
| Licensing | Permission set licenses purchased and available in sufficient quantity | ☐ |
| Licensing | Permission set licenses assigned to pilot users | ☐ |
| Licensing | Corresponding permission sets assigned to pilot users | ☐ |
| Licensing | Maps Admin permission set assigned to administrators | ☐ |
| Configuration | Maps and Location Services enabled | ☐ |
| Configuration | Permission groups created and users/profiles assigned | ☐ |
| Configuration | Button sets configured and assigned to permission groups | ☐ |
| Configuration | Base objects configured for all needed Salesforce objects | ☐ |
| Configuration | Address and coordinate fields correctly mapped on all base objects | ☐ |
| Data | Geocoding batch run on all relevant records | ☐ |
| Data | Geocoding success rate verified (spot-check sample records) | ☐ |
| Data | Address data quality issues identified and remediated | ☐ |
| Data | Records plotting in expected geographic locations | ☐ |
| Layers | Corporate marker layers created for key use cases | ☐ |
| Layers | Shape layers configured for territories or regions | ☐ |
| Layers | Data layers configured if applicable | ☐ |
| Layers | Folder permissions configured (Corporate and Personal) | ☐ |
| Features | Click2Create field sets configured for Lead or Account | ☐ |
| Features | Check In/Out configured with custom disposition if applicable | ☐ |
| Features | Custom action buttons configured if applicable | ☐ |
| Features | Auto Assignment configured if applicable | ☐ |
| Routing & Schedule | Route defaults configured (transportation mode, start location, stop duration) | ☐ |
| Routing & Schedule | Schedule calendar sync configured (Outlook or Google) if applicable | ☐ |
| Routing & Schedule | Maps Advanced visit plans configured if applicable | ☐ |
| Security | Routing role security setting configured per requirements | ☐ |
| Security | Debug Logs confirmed disabled (unless actively troubleshooting) | ☐ |
| Security | Folder Administrator permission assigned only where needed | ☐ |
| Security | PKCE settings verified if enforced org-wide | ☐ |
| Security | UserRole query permission verified if Show User Folders or Routing Role Security enabled | ☐ |

## Testing and Validation

Testing and Validation Checklist   
| Category | Item | Complete |
| --- | --- | --- |
| Admin Testing | End-to-end smoke test completed in production | ☐ |
| Admin Testing | Test user can successfully open Salesforce Maps | ☐ |
| Admin Testing | Records plot correctly on map | ☐ |
| Admin Testing | Layers load and appear correctly | ☐ |
| Admin Testing | Click2Create creates records successfully | ☐ |
| Admin Testing | Check In/Out logs activities correctly | ☐ |
| Admin Testing | Routes build and optimize with correct drive time/mileage | ☐ |
| Admin Testing | Search returns expected results (POI, records) | ☐ |
| Pilot Testing | Pilot user group identified and licensed | ☐ |
| Pilot Testing | Pilot users completed initial training | ☐ |
| Pilot Testing | Pilot users successfully performed core workflows | ☐ |
| Pilot Testing | Pilot feedback collected and documented | ☐ |
| Pilot Testing | Critical issues from pilot resolved | ☐ |
| Mobile Testing | Maps Mobile tested on iOS devices (if applicable) | ☐ |
| Mobile Testing | Maps Mobile tested on Android devices (if applicable) | ☐ |
| Mobile Testing | Check In from mobile device verified | ☐ |
| Mobile Testing | Current location accuracy verified on mobile | ☐ |
| Mobile Testing | Mobile performance acceptable with configured layers | ☐ |

## Training and Documentation

Training and Documentation Checklist   
| Category | Item | Complete |
| --- | --- | --- |
| End-User Training | Training materials created for field reps (plot territory, build route, and check in or out) | ☐ |
| End-User Training | Training materials created for sales managers (territory review and route oversight) | ☐ |
| End-User Training | Training sessions scheduled for rollout waves | ☐ |
| End-User Training | Quick reference guides created (one-page SOPs) | ☐ |
| End-User Training | Demo recordings or videos created for common tasks | ☐ |
| Admin Documentation | Configuration documentation completed | ☐ |
| Admin Documentation | Permission group matrix documented | ☐ |
| Admin Documentation | Base object configuration documented | ☐ |
| Admin Documentation | Layer naming conventions documented | ☐ |
| Admin Documentation | Troubleshooting guide created with FAQs from pilot | ☐ |
| Support | Support channel identified (help desk, Slack, email) | ☐ |
| Support | Support team trained on common issues | ☐ |
| Support | Escalation path to Salesforce Support documented | ☐ |

## Change Management

Change Management Checklist   
| Category | Item | Complete |
| --- | --- | --- |
| Communication | Stakeholder communication plan created | ☐ |
| Communication | Go-live announcement drafted (emphasizing benefits) | ☐ |
| Communication | Leadership briefed on rollout plan and success criteria | ☐ |
| Communication | End users notified of upcoming changes and training | ☐ |
| Rollout Plan | Phased rollout plan documented (waves, timelines) | ☐ |
| Rollout Plan | Success criteria defined and measurable | ☐ |
| Rollout Plan | Rollback plan documented in case of critical issues | ☐ |
| Rollout Plan | Go-live date selected (avoid peak business periods) | ☐ |
| Adoption | Adoption metrics identified (weekly active users, routes created, check-ins logged) | ☐ |
| Adoption | Reporting dashboard created to track adoption | ☐ |
| Adoption | Weekly adoption review meetings scheduled for the first month | ☐ |
| Adoption | Feedback collection mechanism established (survey, office hours) | ☐ |

## Ongoing Maintenance

Ongoing Maintenance Checklist   
| Category | Item | Complete |
| --- | --- | --- |
| Release Management | Process established to review Maps release notes | ☐ |
| Release Management | Custom permission sets (if used) flagged for manual updates each release | ☐ |
| Release Management | Sandbox testing scheduled for each major release | ☐ |
| Data Quality | Quarterly address data quality reviews scheduled | ☐ |
| Data Quality | Periodic geocoding batch runs scheduled | ☐ |
| Data Quality | Process to identify and fix failed geocoding records | ☐ |
| Configuration Audits | Quarterly configuration audits scheduled (base objects, layers, permission groups) | ☐ |
| Configuration Audits | Process to prune unused or duplicate layers | ☐ |
| Configuration Audits | License usage review process (quarterly) | ☐ |

## Final Go-Live Decision

Before proceeding with full rollout, confirm:

- All items in Pre-Launch Readiness are complete.
- All items in Testing and Validation are complete.
- Training materials and support channels are in place.
- Pilot testing identified no critical blocking issues.
- Stakeholders have approved the go-live.
- Support team is ready to handle increased volume.
- Adoption metrics and reporting are configured.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-salesforce_maps-264-0-0-production-enus/2addcda4-01f0-4f47-83c5-f499a45bf555/images/icon_tip.png)

Tip Start with a small pilot team, resolve issues discovered during pilot testing, and then roll out to the wider organization in phases. Phased rollout reduces risk and helps you refine training and support based on real-world usage feedback.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-salesforce_maps-264-0-0-production-enus/2addcda4-01f0-4f47-83c5-f499a45bf555/images/icon_note.png)

Note Plan your first rollout wave during a low-activity period to allow time for users to adjust and for your support team to handle questions.

## Post-Launch Activities

**Within the first week:**

- Monitor adoption metrics daily.
- Hold daily stand-ups with the support team.
- Address critical issues immediately.
- Send a thank-you message to pilot users.

**Within the first month:**

- Review adoption metrics weekly.
- Collect and analyze user feedback.
- Identify and address training gaps.
- Celebrate early wins and share success stories.
- Plan the next rollout wave.

**Within the first quarter:**

- Complete rollout to all planned user groups.
- Conduct the first configuration audit.
- Measure outcome metrics (visits per rep and drive time reduction).
- Share results with leadership.
- Transition to the ongoing maintenance schedule.