What should we do initially with already existing contacts?
- Connectors
- Salesforce Contacts
- Salesflare Contacts
- Salesforce Contacts and Salesflare Contacts Sync
LOOKING FOR PARTNERS 🤝
We're currently looking for partners and distributors in different regions. If you're interested, please feel free to contact us.
Sync Salesforce and Salesflare Contacts
Learn how to sync your Salesforce and Salesflare contacts using the SyncPenguin platform
Many businesses end up with contacts in both Salesforce and Salesflare. A subsidiary or small sales team may prefer Salesflare's simple, automated CRM while headquarters or customer success runs on Salesforce. Other companies are moving from one CRM to the other. In both cases, contact details quickly drift apart between the two systems. Teams waste time exporting and importing CSV files, fixing duplicates and asking each other for the latest phone number or email. Without an automatic connection, neither CRM can be fully trusted.

How SyncPenguin helps
SyncPenguin connects Salesforce Contacts and Salesflare Contacts so the same up-to-date contact data is available in both CRMs automatically. You can run a two-way sync or push contacts only one way. An initial merge links existing contacts instead of duplicating them. Companies are linked to the matching Salesforce Account or Salesflare account. Custom fields such as Salesforce picklists and Salesflare dropdowns can be mapped to each other. With no-code filters and rules, you decide exactly which contacts are synced and how fields are transformed. This works for a long-term side-by-side setup or a smooth CRM migration.
Best suited for: Sales teams using both Salesforce and Salesflare. Companies migrating between Salesforce and Salesflare. Sales operations and CRM administrators. Businesses with subsidiaries or departments on different CRMs.
Real-world use cases
Two-way sync between a subsidiary sales team working in Salesflare and headquarters using Salesforce, so both share one consistent contact database.
Migrate from Salesforce to Salesflare (or the other way around) with an initial merge, then keep both CRMs in sync during the transition period.
Sync only Salesflare contacts tagged "Customer" to Salesforce, so customer success and support teams in Salesforce get new clients as soon as sales closes them.
Use a no-code rule to set the Salesforce Lead Source to "Salesflare" for every contact created from Salesflare, so reports show where contacts came from.
Map a Salesforce picklist, such as customer segment or region, to a Salesflare dropdown custom field, so reps in both CRMs can segment contacts the same way.
Sync Salesflare contacts into Salesforce, then push Salesforce contacts to each rep's Microsoft 365 or Outlook contacts, so caller details are available everywhere.
Consolidate contacts from Salesforce and HubSpot into Salesflare with a many-to-one sync, giving a small sales team one complete contact list.
Add new Shopify customers to both Salesforce and Salesflare with a one-to-many sync, so every team sees webshop buyers without manual imports.
Send contacts with a "Newsletter" checkbox in Salesforce or a "Newsletter" tag in Salesflare to a single Mailchimp audience for email campaigns.
Key features
Two-Way Sync
Keep Salesforce and Salesflare contacts aligned in both directions, or choose a one-way flow. New, updated and deleted contacts are handled automatically.
Custom Field Mapping
Map Salesforce custom fields to Salesflare custom fields, including text, number, date, checkbox, picklist/dropdown and multi-select fields.
Company Linking
Contacts are linked to the matching Salesforce Account or Salesflare account by company name. Missing companies are created for you.
No Duplicates
An initial merge links contacts that already exist in both CRMs. After that, every synced pair is tracked, so updates always reach the right record.
No-Code Rules
Filter contacts by tags, lead source, company or custom fields. You can also transform values with no-code rules, without writing a line of code.
Affordable & Scalable
With SyncPenguin you only pay for changes to your data, regardless of how many contacts you have now or will have in the future.
Things to note
Your Salesforce edition must include API access. This is included in Enterprise, Unlimited, Performance and Developer editions, and available for Professional edition as an add-on.
Both Salesforce and Salesflare store one main email address per contact, so one email is synced between them. In Salesflare, a work email is preferred when available.
Phone numbers and addresses are synced by type. Salesforce has Mailing and Other addresses, and Salesflare has home and work addresses. Field mapping lets you choose how they correspond.
Companies are matched by exact name in both CRMs. Keep company names spelled consistently to avoid creating separate Accounts for the same company.
Salesforce requires a last name. If a Salesflare contact only has a first name, it is saved as the last name in Salesforce so the contact can still be created.
Salesflare tags and display names are read-only. You can use them in filters and rules, but they are not written back to Salesflare. Archived Salesflare contacts are treated as removed.
Only contacts are synced. Salesforce Leads, Salesflare opportunities and other CRM objects are not included, and active Salesforce validation or duplicate rules still apply to synced contacts.




