Metadata versus data in a deployment plan
Key Takeaway
Change sets move metadata, not data, so plan a separate data tool for any records.
Every Salesforce deployment plan has to handle two different things: metadata and data. Metadata describes how the org is built and how it works, and data is the business records stored in it. The two move with different tools, so a plan that moves a new custom object from a sandbox to production must also plan separately for any records that object needs.
Metadata versus data
Metadata is data that describes other data. Business data is the records that match your company's business, such as an account, an address, or a product.
The simplest way to tell them apart is field versus value. For example, on the Address object, the fields are schema metadata and the values in them are data:
| Field (schema metadata) | Value (data) |
|---|---|
| Address Type | Mailing address |
| City | Chicago |
| Postal Code | 60106 |
Metadata covers more than objects and fields. Besides the schema, it describes these parts of an org:
- Process metadata describes what happens when a user clicks Save.
- Presentation metadata covers layout.
- Authorization metadata determines user access.
- General configuration covers general settings, for example configuring Chatter to block emoticons in posts.