Two Salesforce orgs, always in sync
SwiftPort runs a background worker every 2 minutes, detecting changes in your source org and pushing them to your target org — automatically, with no code, no middleware, and no data ever touching SwiftPort's servers.
2 min
Sync interval
Bidirectional
Sync direction
0 bytes
Record data stored
Everything you need to configure a sync
Every setting is in the builder. No config files. No SQL. No engineers required.
Runs every 2 minutes
SwiftPort's background worker polls for changes every 2 minutes using Salesforce's SystemModstamp. New and updated records are detected and pushed to the target org without any manual intervention.
Bidirectional sync
A single sync config can push changes both ways — from Org A to Org B and from Org B to Org A. Set independent field mappings for each direction so you're never stuck with a mirror-only setup.
Filters with picklist support
Narrow down which records get synced using field-level filters. For picklist fields, SwiftPort pulls the real values from Salesforce and presents them as a dropdown — no guessing allowed.
Visual field mapping
A drag-and-drop style field mapper shows all fields from both objects side by side. Required fields are flagged. Auto-mapping matches fields by exact name so you don't start from scratch.
Record Type mapping
Map source Record Types to different target Record Types, assign a fixed default, or pass the value through as-is. Essential when your two orgs have different picklist structures.
OwnerId assignment strategy
Choose how owner is set on synced records: fixed user, round-robin across a group, or pass-through from source. Prevents all records landing in one person's queue.
Match strategy for existing records
Already have records in the target org? Configure a match strategy — match by a field value like Email or External ID — so SwiftPort links to the existing record instead of creating a duplicate.
Pre-flight warnings
Before you activate a sync, SwiftPort's AI analyzes your field mappings for type mismatches, required fields that are unmapped, and picklist value gaps — with a Remove & Retest option for each issue.
Set up a sync in 7 steps
The builder guides you through every decision. Each step validates before you can proceed.
Connect your orgs
Click 'Add Org', authorize via Salesforce OAuth on Salesforce's own login page. No credentials touch SwiftPort.
Pick your objects
Choose the source and target object from a searchable dropdown. Accounts, Contacts, Opportunities, custom objects — anything Salesforce exposes.
Set filters
Optionally filter which records get synced. Pick a field, an operator, and a value. Picklist fields show real Salesforce picklist values.
Map your fields
Drag source fields to target fields. Auto-map handles exact-name matches. Required target fields are highlighted. AI flags type conflicts.
Configure Record Types and Owner
Set how Record Types translate and how OwnerId is assigned on newly synced records.
Set match strategy
Tell SwiftPort how to handle records that already exist in the target org to avoid duplicates on first run.
Dry run & activate
Run a dry run to preview what would sync without writing anything. Then activate — the worker picks it up on the next 2-minute cycle.
Logs that actually tell you what went wrong
Every sync run produces a detailed log. You can see which records succeeded, which failed, read the exact Salesforce error, and retry failures without leaving the page. The AI assistant can analyze your logs and explain what's happening in plain English.
- Per-record success logs with timestamps
- Inline error details with Salesforce error codes
- Retry single failed records or retry all failures in one click
- Filter logs by status: Success, Error, Retried
- Countdown to next scheduled run
- Success rate auto-updates after retries
Ready to keep your orgs in sync?
Start free. Connect your first two orgs in minutes. No credit card required.