Custom fields, validation rules, flows, page layouts, and permission sets define how Salesforce behaves. When they change — accidentally or otherwise — Sesame Software shows you exactly what changed and restores the previous state in minutes.
See Metadata Backup in Action →A corrupted or misconfigured Salesforce org can be as damaging as data loss — broken integrations, failed validation rules, missing fields, and altered permission sets can bring operations to a halt. Sesame Software backs up your complete org configuration alongside your records, so both are always recoverable.
See how Sesame Software captures, compares, and restores Salesforce org configuration — in a 30-minute personalized technical walkthrough.
30 minutes · No commitment · Response within 1 business day
What Is Salesforce Metadata
In Salesforce, metadata is everything that defines how your org works — not the records in it, but the structure around them. Custom fields, validation rules, page layouts, flows, Apex classes, triggers, permission sets, profiles, and record types are all metadata.
Salesforce does not automatically back up metadata. A deployment that removes a field, a change that breaks a validation rule, or an admin who modifies a permission set incorrectly can alter your org in ways that are difficult to identify and expensive to reverse — without a metadata backup.
Sesame Software Backs Up
What Goes Wrong Without Metadata Backup
A release includes a metadata change that deletes or deactivates a field. Without a snapshot of the previous state, identifying exactly what changed and reversing it requires manual investigation across your entire org.
A modified validation rule causes an API integration to start failing silently. No error is obvious until data corruption is discovered downstream — and reverting the rule requires knowing exactly what it said before.
An admin modifies a permission set or profile incorrectly, removing access for a team. Without a metadata snapshot, restoring the previous permission configuration is guesswork.
A flow is modified during a sprint and the change causes incorrect automation behaviour. Without version history on the flow, diagnosing what changed and rolling back is a developer-intensive effort.
Recognized by the People Who Use Us
Enterprise IT teams consistently rate Sesame Software for best support, highest user adoption, and fastest implementation.
Read our reviews on G2 →Visual Metadata Compare
Sesame Software captures your full org configuration automatically and lets your IT team compare any two snapshots side by side — so a changed validation rule, a modified field, or a rewritten flow is immediately visible without digging through Salesforce setup logs.
Three configuration changes identified immediately. Restore any of them individually without touching the rest of your org.
Metadata Backup and Recovery Features
Every capability your IT team needs to back up, compare, restore, and audit Salesforce metadata — alongside complete data backup and recovery in a single platform.
Sesame Software captures your complete Salesforce org configuration automatically — simply set your schedule and let the platform do the rest. Every snapshot is timestamped and available for comparison or restore.
Compare any two metadata snapshots side by side and see exactly what changed — field by field, rule by rule, class by class. Changes are highlighted immediately so your team doesn't have to hunt through Salesforce setup logs.
Restore a specific validation rule, field configuration, or permission set to a previous state without touching anything else in your org. Surgical precision for configuration recovery — the same granular approach as your data restores.
Every metadata change is logged with timestamp and context — giving compliance teams a complete, auditable history of org configuration changes to support change management and regulatory requirements.
Metadata backup and data backup in a single platform. One vendor, one contract, one support team. Your records and your org configuration are protected, compared, and restored from the same interface.
Metadata snapshots are stored in your own environment — AWS, Azure, or on-premise. Your configuration history never passes through or is stored on Sesame servers. Full data sovereignty.
Use Cases
These are the scenarios every enterprise IT team managing Salesforce will eventually face. The difference between a quick fix and a multi-day incident is whether a metadata snapshot exists.
A deployment changes or removes metadata components unexpectedly. Without a snapshot of the previous state, reversing the change means manually reconstructing what was there before.
A permission set is modified, a validation rule is disabled, or a flow is altered outside of the change management process. Without a metadata history, detecting and reversing the change is manual.
Many regulated industries require documented evidence that Salesforce configuration changes were controlled, reviewed, and reversible. Native Salesforce setup audit trails are limited in scope and retention.
After a sprint deployment, your team needs to confirm that only the intended metadata components were modified and nothing else was inadvertently altered in the process.
Metadata Coverage
Salesforce's Metadata API exposes well over 700 metadata types. Vendors that advertise metadata backup often cover a small fraction of them — enough to claim the feature, not enough to reconstruct a customized org. Because coverage is rarely published, the gap usually surfaces during an actual recovery, which is the worst possible time to find it.
Any vendor on your shortlist should be able to state how many metadata types they capture and name the ones they don't. Get it in writing before you sign — including from us. A vendor that gets vague on this question is telling you something useful.
A backup that captures fields but not the flows referencing them, or layouts but not the permission sets governing them, restores an org that looks right and behaves wrong. The failure shows up as broken automation days later, not as an error at restore time.
Metadata coverage that requires someone to register each new component is coverage that decays. Sesame Software picks up configuration changes on the existing schedule — a custom field added during a sprint is in the next snapshot without anyone updating a backup profile.
On some platforms, backing up metadata is included but comparing two snapshots to find what changed is priced separately. Without compare, a metadata backup is an archive you can't read. Sesame Software includes visual compare on every tier.
Configuration Snapshots
Each snapshot is a complete, timestamped picture of your org configuration at that moment. Kept in sequence, they become a change history you can search, compare, and restore from — which is what turns metadata backup from insurance into an operational tool your team uses on ordinary weeks, not just during incidents.
Not just current against last night. Compare this morning against the state before a release six weeks ago, and see every difference between them.
Roll back the one validation rule that broke an integration and leave every other change from that deployment in place. No all-or-nothing configuration restore.
Snapshot before deployment, snapshot after, compare. Confirm only the intended components moved — the check that catches unintended changes while they are still cheap to fix.
Your configuration history is stored in your own AWS, Azure, or on-premise storage. It never passes through Sesame servers, and it stays available to you if you switch vendors.
Metadata is one layer of org protection. See full Salesforce org backup and recovery → · See granular record restore →
One Platform. Complete Protection.
Most backup tools cover records or configuration — not both. Sesame Software gives enterprise IT teams complete Salesforce backup and recovery in a single platform.
Trusted by Enterprise IT Teams
"The out of the box features you get with Sesame Software — history tracking, logs, deleted records — are great to have. Audits allow us to detect schema changes."
"Custom objects added in Salesforce are automatically added as new tables in the replicated database. Custom fields added in Salesforce are automatically added as new columns in the replicated database."
"The Sesame Software tool was helpful during the recovery process. Whenever a new field is created, it is automatically included for data retrieval and backup."
Common Questions
Salesforce metadata backup is the process of capturing and preserving your Salesforce org configuration — including custom fields, validation rules, page layouts, flows, Apex classes, triggers, and permission sets. Unlike data backup which protects records, metadata backup protects the structure and behaviour of your Salesforce environment.
Salesforce metadata changes can break integrations, corrupt workflows, remove critical fields, or alter validation rules without warning. Without a metadata backup, a single misconfigured deployment or accidental change can take days to diagnose and reverse. Sesame Software captures your full org configuration automatically so any change can be identified and restored.
Sesame Software backs up your Salesforce org configuration — schema, automation, business rules, UI configuration, and access controls. The visual compare feature shows exactly what changed between any two metadata snapshots. Contact our team to confirm the full list of supported metadata types for your specific org.
Salesforce's Metadata API exposes more than 700 metadata types, and a heavily customized org can depend on a wide range of them — custom objects and fields, flows and process automation, validation rules, page layouts, record types, permission sets, profiles, Apex classes, and triggers. Partial coverage is the common failure mode: the backup captures fields but not the automation referencing them, so a restored org looks correct and behaves incorrectly. When evaluating any vendor, including Sesame Software, ask for the number of metadata types covered and the specific exclusions in writing, and confirm whether comparing two snapshots is included or priced as an add-on. A metadata backup you cannot compare is an archive you cannot read.
Records and configuration are interdependent. If a field was removed, a record type changed, or a validation rule tightened after your backup was taken, restoring records into the current org can fail outright or silently write incorrect data. Metadata recovery lets your team first establish what changed in the org configuration, restore the relevant components, and then restore records into a structure that actually accepts them. Sesame Software captures both layers on the same schedule and in the same platform, so the configuration snapshot matching any given data restore point is always available.
Yes. Sesame Software captures metadata snapshots automatically so your IT team can compare the current state of your org against any previous snapshot, identify exactly what changed, and restore the previous configuration. This is particularly useful for reversing failed deployments or unauthorized configuration changes.
Regulated industries often require documented evidence of configuration changes — who changed what, when, and what the previous state was. Sesame Software's metadata backup provides a complete, auditable history of org configuration changes to support regulated change management requirements. Please consult with your compliance team to confirm alignment with your specific regulatory framework.
Yes. Sesame Software provides both data backup and metadata backup in a single platform — near real-time backup of your Salesforce records alongside complete org configuration backup. Both are backed up automatically, with point-in-time restore for records and visual compare for metadata.
Sesame Software backs up your Salesforce records and your org configuration — in a single platform, with visual compare, granular restore, and a compliance-ready audit trail built in.
Book a Metadata Backup Demo →TRUSTED BY PROCTER & GAMBLE · BANK OF AMERICA · U.S. GOVERNMENT