📄️ Data Migration Between Environments
Moving records between orgs is harder than moving metadata. Salesforce record IDs differ in every org, so a naive export/import breaks every lookup and relationship. mtdt.io migrates data while keeping those relationships intact.
📄️ Backing Up Salesforce Data Records
Metadata backups protect your org's configuration. Data backups protect your *records — Accounts, Contacts, custom objects, and the relationships between them. mtdt.io* captures record data on a schedule and lets you restore it back into an org when you need it.
📄️ CSV & S3 Data Backups
The simplest way to back up Salesforce records with mtdt.io: export them to CSV files and keep them in object storage — mtdt's own storage, or your own S3-compatible bucket. No database to run; just portable snapshots you can download whenever you need them.
📄️ PostgreSQL Data Backups
Back up your Salesforce records into your own PostgreSQL database — a real, queryable database you control, with a full history of every backup and a precise restore back into an org. This is mtdt.io's smart data backup mode.
📄️ Migrating Salesforce CPQ Data
Salesforce CPQ (the SBQQ package) stores its configuration as records, not metadata — product rules, price rules, discount schedules, configuration attributes, and the web of lookups between them. That makes moving a CPQ setup between orgs notoriously error-prone. mtdt.io packages it into a guided migration.
📄️ Backing Up Salesforce Files
Metadata and record backups don't cover your Files — the attachments, uploaded documents, and images stored as Salesforce Content Versions. mtdt.io backs those up to your own S3-compatible storage, so every layer of your org is protected.
📄️ Backing Up Salesforce Emails
Salesforce logs sent and received emails as EmailMessage records — some of the most compliance-sensitive data in the org. mtdt.io backs them up incrementally to your own PostgreSQL database and S3 storage, giving you a queryable email archive you control.