Lightning Communities Developer Guide

Get Up to Speed with Lightning Communities
Develop Lightning Communities: The Basics
Customize the Look and Feel of a Lightning Template
Example: Build a Condensed Theme Layout Component
Develop Secure Code: Locker Service and Stricter CSP
Analyze and Improve Community Performance
Connect Your Community to Your Content Management System
Report on Deflections: The Deflection Signals Framework
Deploy a Community from Sandbox to Production
Deploy Your Community with Change Sets
Considerations for Deploying Communities with Change Sets
Deploy Your Community with the Metadata API
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Deploy a Community from Sandbox to Production

We recommend creating, customizing, and testing your community in a test environment first, before you deploy it to your production org.
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions

When testing is complete, you can use change sets or the Metadata API to migrate your community from one org to another. Both options are ideal for building and testing a community in a test environment, such as sandbox, and then deploying to another org, such as production.

  • Change sets—If you’re more comfortable working with point-and-click tools, then change sets are your deployment friend.

    Change sets represent sets of customizations in your org (or metadata components) that you can deploy to a connected org.

  • Metadata API—Up to speed on the Metadata API and more comfortable in the world of code? Then use the Metadata API to deploy changes programmatically.

    The Metadata API lets you retrieve, deploy, create, update, or delete customization information for your org, such as communities, custom object definitions, and page layouts.