After 6 posts on Marketing Cloud Connect mechanics, here's the consolidated reference we hand to engineers starting a new MC Connect engagement - component cheat sheet + kickoff checklist.
Components we use most
| Component | Purpose |
|---|---|
| Synchronized Data Extension | CRM object data synced into SFMC as a DE; read-only in SFMC |
| Salesforce Entry Source | Triggers a Journey when a CRM record meets a filter |
| Salesforce Activity | Inside Journey Builder, updates or creates CRM records |
| Marketing Cloud Connect Package | The app installed in Salesforce CRM that enables the integration |
| Integration User | A Salesforce user account the API runs through; needs appropriate permissions |
| Distributed Marketing | Lets CRM users (agents, reps) send from SFMC templates via Salesforce UI |
Each plays a specific role. Knowing which to reach for saves time during design.
Kickoff checklist for MC Connect engagements
[ ] Confirm the client uses Salesforce CRM (Sales Cloud, Service Cloud, Experience Cloud)
[ ] Confirm MC Connect package is installed and configured
(if not, scope includes the install)
[ ] Identify which CRM objects need to sync
(Contact, Lead, Account, Opportunity, custom objects?)
[ ] Identify which fields to sync per object
(Rule: sync only fields you need, not "everything just in case")
[ ] Verify the MC Connect Integration User's permissions
(read on objects, edit on fields that Salesforce Activity will touch)
[ ] Choose sync frequency
(near real-time vs hourly vs daily - pick based on use case)
[ ] Verify Synchronized DEs populate with data before building Journeys
(don't build on an empty DE; test sync first)
[ ] Confirm Journey trigger logic with real records in sandbox
(test every trigger condition, not just the happy path)
[ ] Plan for real-time data scenarios
(if any data must be fresher than sync cycle, plan API lookups separately)
[ ] If Distributed Marketing is in scope, plan training and template governance
Common engagement flow
Week 1: Discovery + permissions
- Confirm CRM / SFMC licenses cover MC Connect
- Map the CRM objects and fields in scope
- Get the Integration User created with correct permissions
- Confirm all environments (production, sandbox) are accessible
Week 2: Sync setup + verification
- Configure Synchronized DE for each object
- Set sync frequency per object
- Wait for initial sync to populate
- Validate row counts and sample records
- Document the schema (field names, data types) for developers
Week 3-4: Build Journeys + Activities
- Build Salesforce Entry Source Journeys for the triggered campaigns
- Add Salesforce Activity writes-backs where needed
- Test end-to-end in sandbox with synthetic records
Week 5-6: UAT + production cutover
- Run UAT with the client using real-looking data in sandbox
- Verify timing - how quickly do CRM events trigger Journeys?
- Move to production with a phased rollout if possible
- Monitor the first week closely
Reference: things that don't belong in MC Connect
Some use cases look like they need MC Connect but don't:
- Non-Salesforce CRM (HubSpot, Dynamics) - use REST API or middleware.
- Non-real-time CRM snapshots delivered as files - regular Import Activity is cheaper than configuring a full MC Connect sync.
- Computed fields that need to be derived from multiple CRM objects - do the computation in Salesforce first (formula field, Flow), then sync the computed field, not raw fields.
- Complex data joins across many CRM objects - pre-compute a flat view in Salesforce (reports or APEX) and sync that view, rather than syncing many objects and joining in SFMC.
When the integration breaks
Most MC Connect issues come from one of four causes:
- Integration User permissions - audit first.
- Sync cycle delays - what you expected to be immediate is actually 30 minutes.
- Field mappings - a field renamed on the CRM side wasn't updated in the sync config.
- Sandbox/production drift - sandbox MC Connect points at sandbox CRM, production MC Connect points at production CRM; configs can drift.
First-response playbook: check the Integration User first, then sync status in Contact Builder, then mapping, then sandbox/production alignment.
Takeaway
MC Connect is a set of maybe six components you'll use repeatedly on Salesforce + SFMC engagements. Knowing what each does and running through the kickoff checklist saves the mid-project surprises. Pin this reference in the team wiki and revisit it on every new engagement.
Running an SFMC + CRM integration project? Our Salesforce team ships end-to-end MC Connect builds - discovery, permissions, sync config, and Journey setup - on production engagements. Get in touch ->
See our full platform services for the stack we cover.
