Import from Salesforce
One-time migration from Salesforce into Harmonia. No ongoing sync — Harmonia replaces SF, not extends it.
If you're coming from Salesforce, Harmonia provides a one-time importer that moves your contacts, accounts, opportunities, activities, and notes into Harmonia. This is a migration, not a sync. Once you commit, Salesforce is your historical archive and Harmonia is your system of record.
Why we don't sync
Two-way sync between CRMs creates a never-ending conflict-resolution problem: which side is canonical? what happens when a field gets edited in both places? what about deletes? Every team that's tried it has eventually picked one side and let the other go stale.
Harmonia's stance is that if you've decided to leave Salesforce, you should leave Salesforce. The importer makes that move clean — keep SF read-only for a few months as an audit trail, but stop writing to it. New work happens in Harmonia.
What the importer brings over
| Salesforce object | Harmonia destination |
|---|---|
Contact | Contacts |
Lead | Contacts (with lead tag) |
Account | Companies |
Opportunity | Opportunities |
Task | Tasks (linked to contact/opportunity) |
Event | Calendar events |
Note | Notes (linked to contact) |
Attachment / ContentDocument | Files attached to contacts |
EmailMessage | Conversation history |
Custom fields | Mapped to Harmonia custom fields |
Reports, dashboards, flows, validation rules, Apex, and Visualforce are not migrated. Those concepts don't map one-to-one. Most reports can be rebuilt in Harmonia's reporting module in less time than it took to write them originally.
Run the import
- Open Integrations → Salesforce.
- Click Start migration. You'll be redirected to Salesforce OAuth.
- Grant read access. Harmonia never writes to Salesforce.
- Pick which objects to import. Default: everything.
- Map any custom fields. The importer auto-creates Harmonia custom fields for any unmapped SF fields.
- Review the dry-run report — how many contacts, opportunities, etc. will land — and the list of any unmappable records.
- Click Run import.
The import runs in the background. You'll get an in-app notification when it finishes; typical org with 50k records completes in 10-30 minutes.
After the import
- Verify — spot-check a few high-value records to confirm fields landed correctly.
- De-duplicate — Salesforce orgs accumulate dupes. Run Contacts → De-duplicate to merge.
- Reconfigure pipelines — your SF opportunities arrive in a default pipeline. Move them into the pipelines you actually want.
- Archive SF access — keep Salesforce read-only for 90 days as a fallback, then cancel.
If something goes wrong
Imports are idempotent — you can re-run safely without creating duplicates. The importer keeps a mapping table between Salesforce IDs and Harmonia IDs, so re-running updates existing Harmonia records rather than creating new ones.
If a partial import lands in a bad state, contact support with your import run ID (visible in the migration history page) and we can roll back to a clean slate.