CRM migration
Field-level mapping, validation, and rollback between FunnelMaker and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
FunnelMaker
Source
Salesforce Sales Cloud
Destination
Compatibility
11 of 15
objects map 1:1 between FunnelMaker and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from FunnelMaker to Salesforce is a structural migration complicated by FunnelMaker's absence of a publicly documented REST API or developer portal. Export relies on in-product CSV downloads and, where available, Zapier or Make integrations. We work with FunnelMaker's export tooling to extract Contacts, Companies, Opportunities, Pipelines, Activities, Custom Objects, and Tags, then map each record to its Salesforce equivalent. FunnelMaker's drag-and-drop pipeline stages translate to Salesforce Record Types and Sales Processes. FunnelMaker's unlimited-user model on a per-contact tier means teams often carry a smaller per-seat cost in FunnelMaker; Salesforce's per-user pricing at Professional ($80/user/mo) and above offsets that with unlimited pipelines, a 9,000+ AppExchange listing ecosystem, and a documented Bulk API 2.0 for activity migration. Workflows, drip campaigns, lead scoring rules, and built-in phone media (call recordings, transcriptions) do not migrate as code or binary files; we deliver written inventories of these for the customer's admin to rebuild in Salesforce Flow.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a FunnelMaker object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
FunnelMaker
Contact
Salesforce Sales Cloud
Lead or Contact
1:manyFunnelMaker Contacts map to either Salesforce Lead (unqualified, early-stage records) or Contact attached to Account (qualified records with a company association). We apply a split rule during scoping based on the customer's FunnelMaker contact lifecycle model. Contacts with a linked FunnelMaker Company record and a closed or advanced stage property map to Contact with AccountId resolved; Contacts without a Company link or in early stages map to Lead. The original FunnelMaker contact stage and any lead score value migrate to a custom field for audit.
FunnelMaker
Company
Salesforce Sales Cloud
Account
1:1FunnelMaker Company records map directly to Salesforce Account. The Company name becomes Account Name; the Company domain or website becomes the Account Website field used as a dedupe key during import. We create the Account record before the Contact phase so that AccountId is available at Contact insert time. All Company-level custom fields (address, industry, employee count) map to typed Salesforce Account fields or custom fields.
FunnelMaker
Opportunity
Salesforce Sales Cloud
Opportunity
1:1FunnelMaker Opportunity records map to Salesforce Opportunity. The Opportunity name, amount, close date, owner, and custom fields migrate directly. We resolve FunnelMaker owner email to Salesforce User ID before import so OwnerId is populated. Closed-won and closed-lost status from FunnelMaker map to the equivalent Salesforce StageName values. Any Opportunity-level custom fields preserve their FunnelMaker values in Salesforce custom fields of matching type.
FunnelMaker
Pipeline
Salesforce Sales Cloud
Record Type + Sales Process
lossyEach FunnelMaker Pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the FunnelMaker pipeline stage values as Salesforce StageName entries. We configure the Record Type, assign Page Layouts, and set the stage probability values before migration begins. Probability percentages round to the nearest integer allowed by Salesforce.
FunnelMaker
Activity: Call
Salesforce Sales Cloud
Task (TaskSubtype = Call)
1:1FunnelMaker call logs (from the built-in click-to-dial feature) migrate to Salesforce Task with TaskSubtype set to Call. Call duration, timestamp, owner, and linked contact reference migrate to custom Task fields (call_disposition__c, call_duration_seconds__c). ActivityDate is set to the original FunnelMaker call timestamp to preserve the timeline. Audio recordings and transcription text are not migrated due to file size, format variability, and compliance constraints.
FunnelMaker
Activity: Email
Salesforce Sales Cloud
EmailMessage + Task
1:1FunnelMaker email activity migrates to Salesforce EmailMessage records (the email body and headers) linked to a Task record for the activity timeline. WhoId on Task points to the converted Lead or Contact; WhatId points to the related Opportunity or Account. Subject, body, sender, recipient, and timestamp transfer directly. EmailMessage records preserve thread continuity for follow-on emails.
FunnelMaker
Activity: Task
Salesforce Sales Cloud
Task
1:1FunnelMaker tasks map to Salesforce Task with Status, Priority, ActivityDate, and subject preserved. Task owner migrates by resolving FunnelMaker owner email to Salesforce User ID via the User mapping. Any FunnelMaker task custom fields map to Salesforce Task custom fields of equivalent type.
FunnelMaker
Activity: Note
Salesforce Sales Cloud
Note
1:1FunnelMaker notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note title, body (rich text), and timestamp transfer directly. Any inline image attachments in FunnelMaker notes become separate ContentDocument records linked to the same parent.
FunnelMaker
Activity: Meeting
Salesforce Sales Cloud
Event
1:1FunnelMaker meeting records migrate to Salesforce Event. StartDateTime, EndDateTime, Subject, Location, and description transfer directly. EventRelation records link attendees to the converted Lead, Contact, or User. The meeting type or outcome from FunnelMaker maps to a custom Event field for categorization.
FunnelMaker
Custom Object
Salesforce Sales Cloud
Custom Object
1:1FunnelMaker unlimited user-defined fields and custom objects migrate to Salesforce Custom Objects with __c API names matched to the FunnelMaker object names. We pre-create the destination schema during discovery: all custom fields with Salesforce field types (text, number, picklist, date, lookup), validation rules, and page layouts are deployed into a Sandbox org before data import begins. Custom object records import last because they frequently have lookup dependencies on standard objects.
FunnelMaker
Lead Scoring
Salesforce Sales Cloud
Custom Number Field on Lead/Contact
1:1FunnelMaker lead scores calculated from customizable demographic and behavioral rules migrate as numeric property values on the Salesforce Lead or Contact record (score__c). The scoring rule logic itself (weighting, thresholds, contributing factors) is documented in a written handoff document that the customer's admin uses to rebuild equivalent Salesforce Flow scoring logic post-migration. The raw score values transfer immediately; the rules require rebuild.
FunnelMaker
Drip Campaign
Salesforce Sales Cloud
Salesforce Flow (documented rebuild)
lossyFunnelMaker drip campaigns (email sequences tied to contact segments and time-based delays) have no direct Salesforce equivalent as a migrated artifact. We extract the campaign structure: segment criteria, step sequence, step timing, email content summary, and associated contact lists. This information is delivered as a written drip campaign inventory with a recommended Salesforce Flow sequence equivalent for each campaign. The customer reviews and rebuilds each sequence in Salesforce Flow, Flow Builder, or a sales engagement tool like Sales Engagement (High Velocity Sales).
FunnelMaker
Tag / Group
Salesforce Sales Cloud
Campaign or Custom Field
lossyFunnelMaker Tags and Groups used for contact segmentation migrate to Salesforce Campaigns (for list-based segmentation) or to multi-select picklist fields on Contact and Lead (for field-based tagging). We inspect the customer's tag usage during discovery to determine which strategy applies. Tags used primarily for marketing list segmentation map to Campaign with CampaignMember records; tags used as CRM attributes (industry tag, role tag) map to multi-select picklist fields.
FunnelMaker
Document
Salesforce Sales Cloud
ContentDocument
1:1FunnelMaker documents (stored files and signature requests) migrate as Salesforce ContentDocument records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity record. Document metadata (file name, type, size, upload date, signature status) transfers to Salesforce ContentVersion and ContentDocument fields. File content transfers where FunnelMaker export access is available; customers with restricted file access export documents manually and we associate them post-import.
FunnelMaker
Owner
Salesforce Sales Cloud
User
1:1FunnelMaker record owners (assigned by email) map to Salesforce User records by email match. Any FunnelMaker owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import continues. Inactive FunnelMaker owners map to an inactive Salesforce User or a System User placeholder to preserve the owner attribution without blocking the import.
| FunnelMaker | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Contact | Lead or Contact1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Opportunity | Opportunity1:1 | Fully supported | |
| Pipeline | Record Type + Sales Processlossy | Fully supported | |
| Activity: Call | Task (TaskSubtype = Call)1:1 | Fully supported | |
| Activity: Email | EmailMessage + Task1:1 | Fully supported | |
| Activity: Task | Task1:1 | Fully supported | |
| Activity: Note | Note1:1 | Fully supported | |
| Activity: Meeting | Event1:1 | Fully supported | |
| Custom Object | Custom Object1:1 | Fully supported | |
| Lead Scoring | Custom Number Field on Lead/Contact1:1 | Mapping required | |
| Drip Campaign | Salesforce Flow (documented rebuild)lossy | Fully supported | |
| Tag / Group | Campaign or Custom Fieldlossy | Fully supported | |
| Document | ContentDocument1:1 | Fully supported | |
| Owner | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
FunnelMaker gotchas
Contact tier limits are hard caps, not soft limits
No publicly documented API for direct export
Workflow and drip campaign migration requires manual sequencing
Built-in phone features do not export call recordings or transcription text
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Discovery and FunnelMaker export preparation
We audit the source FunnelMaker account across all tiers, custom objects, pipeline count, active workflows, drip campaigns, tags and groups, and activity volume. Because FunnelMaker has no API, we coordinate with the customer to run in-app CSV exports for each object. We inspect the export schema during discovery, identify any fields or objects not covered by standard exports, and request manual exports for gaps (custom objects, documents). We also confirm the FunnelMaker pricing tier and contact count to flag any tier-ceiling risks before export begins. The discovery output is a written migration scope and an export checklist for the customer to complete.
Salesforce schema design and sandbox provisioning
We design the destination Salesforce schema based on the exported FunnelMaker data. This includes provisioning any needed Custom Objects, custom fields (with Salesforce field types matched to FunnelMaker field types), Record Types per FunnelMaker Pipeline, Sales Processes with stage whitelists, Page Layouts per Record Type, and the Lead-Contact split rule derived from the FunnelMaker lifecycle model. Schema is deployed via Salesforce metadata API or change set into a Salesforce Sandbox first for validation. We coordinate with the Salesforce admin on validation rules and field-level security settings that may need adjustment for the migration user.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-equivalent data volume extracted from FunnelMaker. The customer's RevOps lead reconciles record counts (Contacts in, Leads in, Accounts in, Opportunities in, Activities in), spot-checks 25-50 random records against the FunnelMaker source, and validates the Lead-Contact split, pipeline stage mapping, and owner attribution. Any mapping corrections are made in this phase before production migration begins. This sandbox run also surfaces any Salesforce validation rule failures that need admin resolution.
Owner reconciliation and User provisioning
We extract every distinct FunnelMaker record owner referenced across Contacts, Companies, Opportunities, and Activities and match them by email against the Salesforce destination org's User table. Owners without a matching User go to a reconciliation queue for the customer's Salesforce admin to provision before record import proceeds. OwnerId is required on most standard objects, so this step must complete before the production migration run begins.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from FunnelMaker Companies), Leads and Contacts (with AccountId resolved for Contacts, Lead-Contact split applied), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Activities via Bulk API 2.0 (Tasks, Events, EmailMessages, Notes with chunking and parent-record resolution), Custom Objects last (because they often have lookup dependencies on standard objects). Each phase emits a row-count reconciliation report before the next phase begins. We use exponential backoff on API limit responses and batch chunking for large activity histories.
Cutover, validation, and workflow handoff
We freeze FunnelMaker writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record. We deliver the workflow and drip campaign inventory document to the customer's admin team. We support a one-week hypercare window to resolve reconciliation issues raised by the customer's team. We do not rebuild FunnelMaker workflows as Salesforce Flow inside the migration scope; that is a separate engagement. Reports and dashboards from FunnelMaker do not migrate; we deliver a written list of the existing reports for the admin to recreate in Salesforce Reports and Dashboards.
Platform deep dives
FunnelMaker
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across FunnelMaker and Salesforce Sales Cloud.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
FunnelMaker: Not publicly documented.
Data volume sensitivity
FunnelMaker doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during FunnelMaker to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your FunnelMaker to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave FunnelMaker
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.