If you’ve got customer data in Salesforce and you’re using Momentum to help your sales or ops teams, you already know the pain: double entry, mismatched fields, “wait, where’s that note?” headaches. This guide is for anyone who wants Salesforce and Momentum to actually talk to each other, without days lost to setup or “consultant” bills. You’ll get step-by-step instructions, a few honest warnings, and tips for not making things harder than they need to be.
Before You Start: What You Need (and What to Skip)
Before you dive in, let’s clear up what you actually need:
- Admin access to both Salesforce and Momentum. Doesn’t matter if you’re a power user, you’ll need admin rights for setup.
- A clear idea of which data you want to sync. Don’t just “sync everything.” Pick the objects and fields that matter—usually leads, opportunities, and maybe some custom fields.
- A test Salesforce account (sandbox) if possible. You do not want to experiment on your live data.
Skip: - Fancy data mapping diagrams (at least for your first pass). - Buying extra integration platforms unless you really need them. Momentum has native Salesforce integration—start there.
Step 1: Decide What’s Actually Worth Syncing
Here’s a hard truth: syncing everything sounds nice, but it’s usually a mess. Start with:
- Core objects: Leads, Contacts, Opportunities.
- Essential custom fields: Only the ones teams actually use.
- Notes and activities if your reps rely on them.
Pro tip: Write down exactly what you want to sync and why. This keeps things sane later.
Step 2: Enable Salesforce Integration in Momentum
Momentum’s Salesforce integration is built-in, but not always enabled by default. Here’s what to do:
- Log into Momentum with admin credentials.
- Navigate to Settings (look for the gear icon, usually top right).
- Find “Integrations” and click “Salesforce.”
- Click “Connect Salesforce.” You’ll be asked to log in with your Salesforce admin account and grant permissions.
- Approve the requested permissions. Don’t blindly click “allow all”—read what Momentum is requesting. If something looks off, ask your IT/security team.
What to watch for:
- If you use Salesforce “sandbox,” make sure you’re connecting to the right environment.
- If you get an “insufficient permissions” error, you probably need a full admin role in Salesforce.
Step 3: Map Your Fields (Don’t Overthink It)
Now Momentum will ask you what to sync. Here’s where people get stuck trying to make every field line up perfectly. Don’t.
- Start with the basics: Name, email, company, deal stage, owner.
- Momentum will try to auto-map fields. Check these line by line. If something’s missing, add a custom mapping.
- Leave “weird” fields for later: If you’re not sure what a field does, skip it for now. You can always add more mappings after the basics work.
Pro tip:
Momentum sometimes tries to map fields based on similar names, but it’s not always right. Double-check dates, picklists, and anything custom.
Step 4: Set Up Data Sync Rules
This is where you decide what pushes where. Most teams want:
- Two-way sync: Changes in either system update the other. Good for most sales workflows.
- One-way sync: For data you only want to flow one direction. For example, maybe you want notes to go from Momentum → Salesforce, but not the other way.
How to do it:
- In Momentum’s Salesforce integration settings, look for “Sync rules” or “Direction.”
- For each object (Leads, Opportunities, etc.), set if you want one-way or two-way sync.
- Set conflict resolution. (E.g., if the same field changes in both places, which wins? Usually, “most recent change” is safest.)
Heads up:
- Two-way sync is great, but it can create loops if you have automation rules firing on both sides. Test carefully.
- If you’re unsure, start with one-way sync from Salesforce → Momentum. You can always open up two-way sync later.
Step 5: Test With Real Data (But Not Live Data)
Don’t hit “sync all” until you’ve tested with a handful of records.
- Pick 2-3 records (leads or deals with real data, but not live prospects).
- Update a field in Salesforce. See if it shows up in Momentum.
- Change the same field in Momentum. See if it updates in Salesforce, if you set up two-way sync.
- Check for mismatches: Pay special attention to picklist values, date formats, and any custom fields.
What usually goes wrong: - Picklist fields don’t match (e.g., “Closed Won” in Salesforce, “Won” in Momentum). - Permissions errors block sync for some users. - Custom fields in Momentum don’t exist in Salesforce (or vice versa).
Fix these before rolling out to your whole team.
Step 6: Roll Out (Carefully)
Once you’ve tested, it’s time to let more users in.
- Start with a small group. Let 3-5 power users use the integration for a week.
- Ask for feedback: Did anything break? Are notes syncing correctly? Is data ending up in the right place?
- Monitor errors: Momentum should show you sync errors. Don’t ignore them—fix root causes.
Pro tip:
Don’t announce the integration company-wide until you’re sure it’s stable. There’s nothing worse than 50 people emailing you about missing data.
Step 7: Automate the Boring Stuff (If You Want)
Once basic sync works, you can use Momentum’s workflow builder (or Salesforce Process Builder) to automate repetitive tasks. But keep it simple at first:
- Auto-create follow-up tasks when a deal hits a certain stage.
- Sync key fields only when a record is updated, not every time it’s viewed.
- Set up alerts in Momentum if a sync fails (don’t just rely on email).
What to ignore (for now): - Overly complex automations. If you’re writing 10-step flows, you’re probably making things harder than needed. - Third-party automation tools. Momentum’s built-in features cover most needs for small-to-mid teams.
Step 8: Maintain and Monitor
Integrations need babysitting, especially early on.
- Check sync logs weekly for errors or mismatched data.
- Spot-check random records to make sure things still line up.
- Update field mappings if your Salesforce schema changes (new custom fields, renamed objects, etc.).
Momentum’s support is decent, but don’t expect miracles. If you hit a weird bug, document it and escalate with screenshots.
What Works, What Doesn’t, and What to Watch Out For
Works well: - Standard fields (names, emails, stages). - Basic two-way sync for core objects. - Quick setup if you keep it simple.
Needs attention: - Custom fields and picklists (often need manual mapping). - Large data volumes—Momentum’s sync isn’t built for massive, nightly updates. - Complex automations—can get messy fast.
Ignore (at least for now): - Syncing old, unused fields “just in case.” - Integrating with a dozen other platforms at once. - Trying to replace advanced Salesforce automation with Momentum workflows.
Wrapping Up: Keep It Simple, Iterate Often
Salesforce and Momentum can work together and save you a ton of double work—if you start small and stay focused. Sync only what you need, test with real (but safe) data, and don’t fall for the “sync everything” trap. Integrations aren’t magic, but with a little care up front, you’ll spend less time fixing data and more time actually using it.
If you get stuck, cut back to basics, fix what’s broken, and try again. You’ll get there. And once it’s running smoothly, resist the urge to tinker—at least until you’re sure it’s adding value, not just complexity.