Move your Salesforce data, in bulk, on demand
Whether you're consolidating orgs, refreshing a sandbox, or doing an initial data load, SwiftPort Migrations let you push any object — with filters, field mapping, and match strategy — from one Salesforce org to another. No code. Save and re-run any time.
Any object
Standard & custom
Multi-step
Dependency-aware
Re-runnable
Save & run again
Built for serious data movement
More than a CSV import. A full migration builder with logging, deduplication, and re-runs.
Any Salesforce object
Migrate standard objects (Accounts, Contacts, Leads, Opportunities, Cases) or any custom object. SwiftPort fetches the full schema from Salesforce so you see every field.
Multi-step, dependency-aware
Define multiple object steps in a single migration job. SwiftPort executes them in sequence — so Accounts migrate before Contacts, preserving lookup relationships.
Scoped by filters
Don't move everything — filter which records get migrated. Combine field conditions to select only the records you need, with picklist values shown from Salesforce.
Field mapping per step
Each step gets its own field mapping. Source fields don't need to have matching names in the target org. Auto-map handles exact matches; you handle the rest manually.
Match strategy for deduplication
If records already exist in the target org, configure a match strategy. Match by Email, Account Name, external ID, or any field — so existing records are updated, not duplicated.
Full run history
Every migration run is logged. See how many records were processed, how many succeeded, how many failed, and why — with per-record error details for failures.
Saveable & re-runnable
Migrations are saved to your account. Re-run a migration any time — useful for periodic imports, initial data loads, or syncing environments on demand.
Critical-fail logic
If a critical step fails, the chain stops. Downstream steps that depend on the failed step don't run — preventing partial or inconsistent data states.
Common use cases
Migrations work for any scenario where you need to bulk-move records between orgs.
Org consolidation
Merging two business units that each have their own Salesforce org. Move all historical data into one org before decommissioning the other.
Sandbox refresh population
Production data looks different from sandbox data. Use a migration to pull a representative sample from production into your sandbox for realistic testing.
Data archiving
Move closed or old records out of a busy org into a clean archive org. Reduce clutter and keep your operational org focused on active data.
Initial data load
Going live on a new Salesforce org? Migrate your data from a legacy CRM, spreadsheet import org, or existing org all at once with a single migration job.
Build a migration job in 7 steps
The guided builder walks you through every decision. No SQL, no APIs, no engineers.
Name your migration job
Give the job a clear name. You'll run it more than once so make it meaningful — e.g. 'Production → Sandbox Accounts & Contacts'.
Choose source and target orgs
Select from your connected orgs. The same org can be used for both source and target (useful for testing).
Add steps (objects)
Each step is one object migration. Add as many steps as needed. Order matters — place parent objects before child objects.
Per step: filters and mapping
For each step, configure which records to pull (filters) and how fields map from source to target. Required target fields are highlighted.
Per step: match strategy
Tell SwiftPort how to handle records already in the target org. Match by a field like Email or External ID to avoid duplicates.
Review AI warnings
SwiftPort's AI analyzes your mapping for type mismatches, unmapped required fields, and potential data loss before you run.
Run the migration
Hit Run. SwiftPort executes each step in sequence on the Railway worker. Monitor live progress in the run history view.
Need ordered, dependency-chain migrations?
Migrations also power SwiftPort's CPQ and Revenue Cloud Accelerator (RCA) integration modes. These are pre-built templates that migrate Salesforce CPQ and RCA objects in the correct dependency order — Price Books, Products, Pricebook Entries, Assets, and more.
Every run is logged and inspectable
After a migration runs, you get a full breakdown of every step: how many records were attempted, how many succeeded, and detailed error messages for each failure. You can re-run the entire job or investigate individual steps.
- Per-step success and failure counts
- Salesforce error codes per failed record
- Re-run the full job with one click
- Full history across all runs for each job
Migration Run — Production → Sandbox
Started 2 minutes ago · 3 steps
Ready to move your data?
Start free. Build your first migration job in minutes. No credit card required.