Centric Software · Salesforce + HubSpot Marriage

GoogleSpreadsheet - Logins + Data Mapping

What was built

The discovery and design phase — stakeholder interviews, system architecture mapping, and full data/logic specification before any build work began.

System Stack Mapping

Separate discovery sessions with Contentserv and ShoppingFeed teams to document their existing CRM stacks: HubSpot instance structures, Pardot setup (Contentserv), active workflows, lists, form submissions, lifecycle stage definitions, and field inventories. Outputs were visual architecture maps in Miro.

Stakeholder Sessions

Regular work sessions with sales, marketing, and ops leads across all three companies: José (sales ops), Ryan and Lisa (marketing + sales ops), Mathieu (ShoppingFeed), Sabrina (marketing/scoring), Sagar (field mapping, SF↔HS), Doug (executive steering). Key topics: install base data, quote-to-cash flow, MQL routing, lead scoring approach, notification requirements, and data migration scope.

Field-by-field mapping of HubSpot properties (Contentserv and ShoppingFeed) to Salesforce objects. Separate mapping tabs for contacts and accounts per entity. Properties scoped out in HubSpot for both instances, cross-referenced against Salesforce field availability.

Logic Mapping

Defined rules for: lifecycle stage transitions, MQL routing (form submission → Salesforce lead), email notifications for sales on deal events (Contentserv, ShoppingFeed), termination notifications, and campaign attribution. Risk assessment and phasing plan delivered to steering committee.

Deliverables

Integration architecture design, field mapping spreadsheet, logic mapping document, risk assessment — handed off as the spec for Phase 2 development.