How RetailNext Moved to HubSpot Marketing Hub Enterprise With Salesforce Integration and Lead Scoring

Migration and Scoring Requirements

1. A hard platform deadline with no fallback.

Pardot was sunsetting on a fixed date, with no extension available. Missing that date meant marketing automation would stop entirely, with no interim system to fall back on.

2. A cost-sensitive, scope-limited migration.

The prior migration attempt had already failed over cost overruns and an aggressive timeline. A second failure risked ending the relationship entirely, with no budget appetite for a larger-scope redo.

3. Keeping Salesforce untouched as the system of record.

Any new marketing platform needed a native integration, not a CRM replacement that disrupted the sales team's existing process. Without that constraint, the sales team would have had to re-learn how to work a deal, not just how marketing operated.

4. Historical attribution at risk.

The earlier failed migration had already produced "migrated data" with no usable reporting attached to it. A repeat meant marketing would lose the ability to prove which campaigns drove revenue, going into the new platform blind.

5. Lead scoring that didn't reflect real buying intent.

Pardot's activity-only model produced inflated scores with no decay and no separation between fit and engagement. Sales couldn't reliably tell a genuinely sales-ready account from one that had simply visited the website repeatedly.

RetailNext needed a partner who could execute a scoped migration against a fixed deadline while rebuilding lead scoring around real account fit and intent.

The Solution: How Campaign Creators Rebuilt RetailNext's Marketing Foundation on HubSpot

Campaign Creators sequenced the engagement to hit RetailNext's fixed Pardot sunset deadline: onboarding and setup first, followed by the Salesforce integration, the marketing asset rebuild, and the lifecycle segmentation and lead-scoring build, with consulting and training running alongside.

Standard Objects With Salesforce as System of Record

RetailNext's prior migration attempt had produced unreliable reporting, so the data model needed to preserve attribution without duplicating the sales team's existing Salesforce structure. Campaign Creators used HubSpot's standard objects (Contacts, Companies, Deals, Tickets), not custom objects, keeping Salesforce as the authoritative system of record for CRM and opportunity data while HubSpot owned marketing engagement and campaign data.

Every Sync Error Documented

Campaign Creators configured a native HubSpot-Salesforce integration syncing Contacts, Leads, Accounts, Opportunities, Cases (one-way to HubSpot), and Tasks. After the integration went live, the sync surfaced legacy data issues that hadn't been visible beforehand: 22 Leads and Contacts failed on invalid email addresses, 3,016 Opportunities failed for missing Opportunity Record Type, and 279 Opportunities failed because their associated Account predated 2021 and had never been imported into HubSpot. Each category of error was documented and triaged individually, not suppressed, giving RetailNext a clean, auditable record of legacy data gaps surfaced and tracked, not hidden.

Backfilling 43,000 Blank Company Names Before Launch

Marketing assets, including forms, emails, and landing pages, were rebuilt individually in HubSpot, not bulk-imported, with each asset tracked through sign-off. During migration, the team found that 43,000+ Salesforce-sourced contacts had a blank Company Name field, which would have broken email personalization at launch. Campaign Creators built an automation to backfill the field across the full contact base, closing the gap before launch.

Defining What Fit and Engagement Mean for RetailNext

Lead scoring required defining what "fit" and "engagement" meant for RetailNext specifically, not a generic scoring template. Fit Score properties were built around industry, store count, persona tier, and target-account status; Engagement Score properties were built around form fills, pricing-page visits, and event engagement, each weighted with recency-based decay so that old activity stopped inflating scores indefinitely.

Rolling Contact Scores Up to the Account

RetailNext's buying committees often span several contacts within one account, and Pardot scored each contact in isolation with no way to view them as a single account. Campaign Creators configured the Fit and Engagement model to roll scores up from associated contacts to the company record, so two contacts scoring 50 points each report as a 100-point company score, and three contacts scoring 60 points each report as 180, giving the sales team one account-level view, not several disconnected contact scores.

Timing and Field-Type Mismatches Resolved in Workflow

• A two-minute delay built into lead-routing workflows after a Salesforce campaign-assignment timing issue was found firing HubSpot actions before Salesforce finished assigning the campaign
• New dropdown fields and sync workflows reconciling a State/Country field-type mismatch between HubSpot's text fields and Salesforce's dropdown fields
• Lifecycle-stage advancement workflows tied to the Fit and Engagement scoring thresholds

Four Months of Support Past the Launch Window

Campaign Creators delivered consulting and training sessions running from March through June 2026, well past the initial implementation window, to work through issues as RetailNext's team put the new system into daily use. This included resolving a structural mismatch discovered after launch, in which HubSpot and Salesforce define "campaign" differently, which blocked a direct campaign-data sync and required a new unified campaign-tracking approach built specifically for RetailNext's two-platform setup.