By Daniel Mercer · Updated October 7, 2026

Email marketing for Salesforce users

Salesforce should remain the source of truth for leads, accounts, opportunities, and consent. Your email platform should turn those records into audience segments and measurable journeys without creating a second, conflicting CRM. For a small team, the winning setup is usually a narrow sync, clear field ownership, and a few flows that sales can inspect.

Decide what Salesforce owns

Write down the fields that marketing may read and the fields it may update. A sensible first boundary is Salesforce for account owner, lifecycle stage, opportunity status, lead source, and consent status; the ESP for campaign engagement, delivery events, and temporary journey state. If both systems can edit the same field, a later sync can silently overwrite a lawful opt-out or move a prospect backward in the funnel.

Use a stable contact key, not an email address alone. People change addresses, and one person can appear on a lead and a contact record. Decide how the connector handles merges, duplicate leads, converted leads, and hard bounces. Document the rule in the field description and test it with a small sandbox cohort before you sync the whole org.

Flows that make the CRM connection useful

  1. New lead education. When a lead has consent and a known source, send a short series that answers the question behind that source. Stop the series when a rep logs a meeting, a qualified opportunity opens, or the lead withdraws consent.
  2. Opportunity support. Give prospects a practical comparison, implementation note, or security answer chosen by opportunity type. Sales should see the last message and the next scheduled message in Salesforce so outreach does not collide.
  3. Stalled opportunity check-in. Trigger a human review when an opportunity has had no activity for the agreed period. Let the rep choose whether to send a useful note, reschedule, or close the loop; do not automate pressure into a sensitive account.
  4. Customer onboarding. After a closed-won event, move the record to a customer journey with role-specific setup guidance. Exclude contacts who are already in a support escalation or whose account owner has paused communication.
  5. Expansion and renewal. Use product adoption or contract fields only when they are accurate and current. A renewal reminder should go to the correct business contact, include a human owner, and stop after a renewal or cancellation event.

Example sequence: a small B2B consultancy

Day 0: a lead receives a plain-language guide tied to the campaign that created the record. Day 3: a second message answers the most common implementation question. Day 7: Salesforce checks whether a meeting or opportunity exists; if it does, the automated series ends and the owner receives a task. If not, the prospect receives one case-specific checklist. When an opportunity opens, the ESP suppresses generic education and starts a two-message decision-support branch. A rep can pause the branch from Salesforce without logging into the ESP.

Platform shortlist

PlatformUseful for a Salesforce teamIntegration question
MailchimpFamiliar campaigns and a broad connector ecosystem for a basic nurture program.Which Salesforce fields sync, how often, and how unsubscribes return.
ActiveCampaignDeeper automation when a small sales team owns multiple lifecycle stages.Whether the connector preserves opportunity and owner changes as expected.
HubSpot Marketing HubA strong option when the organization is considering a broader CRM operating model.What remains in Salesforce and how duplicate records are handled.
BrevoUseful for a team that wants campaign sends and straightforward contact segments.Whether your connector covers the consent and custom fields you need.
MailerLiteSimple landing pages and newsletters for a small marketing operation.How much of the workflow must be maintained with an integration service.
GetResponseLanding pages and automation for teams testing a broader acquisition funnel.Which Salesforce events can start or stop journeys.

Costs at three operating sizes

At 1,000 marketable contacts and a few thousand monthly sends, compare the base plan plus the connector or integration service. At 10,000 contacts, model the contact tier, additional seats, and the number of synchronized fields. At 50,000 contacts, add the cost of data operations: monitoring failed syncs, resolving duplicates, and maintaining suppression logic. An apparently inexpensive ESP can become costly if every change needs a manual Salesforce export. Ask each vendor to price the exact audience tier, monthly volume, and number of users you expect to have in the first year.

Migration plan

Export Salesforce field definitions and a consent report before you change providers. Map each field to one owner, then import only records with a documented marketing permission. Recreate one lead nurture and one customer onboarding flow first. Test a new lead, converted lead, closed-won account, hard bounce, unsubscribe, and manual pause. Compare counts in both systems and keep the old connector read-only until the new suppression path has worked for a full campaign cycle.

For adjacent decisions, read the B2B email guide, the startup guide, and our buying guide.

FAQ

Should Salesforce or the ESP own consent?

Choose one authoritative consent field in Salesforce and synchronize it to the ESP. The ESP must still enforce suppression immediately when someone unsubscribes.

Do small teams need a complex automation platform?

Only if the team can maintain it. Start with a few flows and a clear owner; complexity without monitoring creates more risk than value.

How do I prevent sales and marketing messages colliding?

Make sales activity and opportunity state explicit stop conditions. Expose the next scheduled email to the account owner and provide a manual pause control.