Overview
Salesforce remains the enterprise CRM default. Selective sync keeps HelloGrowthCRM aligned for teams in a pilot while headquarters stays on Salesforce—governance and field mapping are the hard parts.
What data is involved
- Accounts, contacts, opportunities, tasks, and events as configured.
- External IDs for stable cross-system linkage.
Step-by-step setup
Setup at a glance (3-5 bullets)
- Settings → Integrations → Salesforce.
- Connect via OAuth or connected app credentials.
- Map objects and enable incremental sync with conflict resolution.
Sign in or sign up at HelloGrowthCRM. Open the login page, enter your credentials (or use Google), or choose Sign up if you need a new account. You must be signed in before you can open Settings and connect this integration.
Open login page(opens in a new tab)app.hellogrowthcrm.com/login
Open Settings. In the left sidebar, under Admin, click Settings (you will land on the Settings area; the URL is app.hellogrowthcrm.com/settings).
Open Settings(opens in a new tab)app.hellogrowthcrm.com/settings
Go to Integrations. On the Settings screen, use the middle settings menu. Under COMMUNICATION, click Integrations (star icon). Then find and configure this connector—the connector-specific steps below pick up from here.
Open Settings (Integrations)(opens in a new tab)app.hellogrowthcrm.com/settings
- Settings → Integrations → Salesforce.
- Connect via OAuth or connected app credentials.
- Map objects and enable incremental sync with conflict resolution.
Best practices
- Involve Salesforce admins on profile and API limit planning.
- Avoid syncing everything—scope to the business units that need it.
Best for & common use cases
Revenue orgs that must keep Salesforce and HelloGrowthCRM aligned during pilots or division rollouts.
- Regional teams on HelloGrowthCRM while HQ remains on Salesforce.
Expected outcomes
- Faster lead handoff between tools and CRM owners
- Cleaner activity history for follow-up and reporting
- Lower manual copy-paste errors in the pipeline
FAQ
Governance
Treat API keys and webhooks as production secrets. Align field mapping with your privacy policy and regional regulations (GDPR, marketing consent, telemarketing rules). Your admin controls which roles can install or edit integrations.