📄️ Deploying Metadata with mtdt.io
Deployments are the core of mtdt.io: move metadata between environments — org to org, or from a Git branch to an org — with a clear review step before anything lands.
📄️ Metadata Backup: How It Works
A metadata backup is a point-in-time snapshot of an org's configuration — Apex, flows, objects, fields, layouts, permission sets, and the rest of your metadata. mtdt.io keeps these snapshots so you can see what changed over time, restore a known-good state, and feed rollbacks.
📄️ Using Diffs to Compare Metadata
Before you deploy — or just to understand how two environments differ — mtdt.io can compare metadata side by side and show you exactly what changed.
📄️ Compare Salesforce Metadata Without Reading XML
Comparing a profile, a picklist, or a page layout as raw Salesforce XML is slow and easy to get wrong — the real change is buried in nested tags and machine ordering. For the metadata types where XML is genuinely hard to read, mtdt.io renders the diff as a structured, clickable view instead: a Table View for fields, objects, layouts, value sets, record types, report types, and Lightning pages, and a permission-manager grid for profiles and permission sets. You review the change by reading rows and pick exactly what to deploy — no XML editing. (Every other metadata type still shows a normal XML diff.)
📄️ Pre-Deployment Checks
Before a deployment runs, mtdt.io checks it against the target org and flags anything risky — missing dependencies, forgotten profiles, no rollback point — so you fix it before you deploy, not after a failed release.
📄️ Detect Target-Org Changes Before a Deploy Overwrites Them
While you compare two orgs and prepare a deployment, the target org keeps living — another admin or developer can edit the very components you're about to push. Deploy anyway and you silently overwrite their work. mtdt.io's Target Org Changes check catches this: before you deploy, it compares each selected item against the target org's current state and flags anything that changed there since your snapshot, so an overwrite becomes a decision instead of an accident.
📄️ Managing Metadata Rollbacks
Even a well-reviewed deployment can have unintended effects in production. mtdt.io lets you undo one by restoring the target org to exactly how it looked before the deployment ran.
📄️ Deployment Approvals
Deployment approvals let your team require a reviewer's sign-off before a deployment runs — role-based separation of duties, with extra protection for your most important orgs.
📄️ Running Apex After a Deployment
Some changes aren't finished when the metadata lands. A scheduled job needs re-scheduling, a custom setting needs a value, a new field needs backfilling. mtdt.io can run a block of anonymous Apex on the target org automatically, right after the deployment succeeds — so the post-deploy step happens as part of the release instead of being a manual thing someone has to remember.
🗃️ Deploying Specific Metadata Types
4 items