Phased approach: Marketo first, Salesforce CRM later, lessons learned? | Community
Skip to main content
H
HimanshuBh4
Level 1
August 18, 2026

Phased approach: Marketo first, Salesforce CRM later, lessons learned?

  • August 18, 2026
  • 1 reply
  • 11 views

We're starting a Marketo implementation where Salesforce integration won't be ready 6-12 months (internal dependencies, not our choice). Rather than wait, we're exploring and planning to:

  1. Launch Marketo standalone (scoring, nurture, events, preference center)
  2. Design everything CRM-ready (fields, lifecycle, program statuses, naming)
  3. Validate scoring before routing leads to sales
  4. Connect SFDC later as a "Phase 2 switch-on"

For those who've done this:

  • What did you build BEFORE CRM that you were glad you did?
  • What caused rework when you eventually connected?
  • Any "I wish I'd known this earlier" advice?
  • How long standalone was enough to validate your scoring model?

Context: Large global B2B firm, but focus is for regional firm.

1 reply

Michael_Florin-2
Michael_Florin-2
Level 10
August 18, 2026

Just two things I’d like to mention:

 

  1. Every person in Salesforce that already exists in Marketo standalone, will become a Marketo duplicate once you sync.
  2. Usually, you create synced fields in Salesforce first. Now you’ll need to create many fields in Marketo first, but since we have the option to merge fields ourselves, we can remedy the situation. I’d recommend to have a list of those Marketo fields that will later on become synced fields.
    Terms & ConditionsAccessibility statement

    Loading footer...