Migrate from Followup CRM to Salesforce Sales Cloud

Followup CRM contacts map 1:1 to Salesforce Contacts. Because Salesforce requires an AccountId for most operations, contacts without a primary company are attached to a default ‘Unassigned Accounts’ record or a fallback mapping rule using an external ID. For contacts tied to multiple companies, we create additional Account Contact Relation records after the primary AccountId is assigned.

If Followup CRM holds both unconverted prospects and existing customers within the same contacts table, we segment them using a status field or tag. Contacts marked as prospects with no closed‑won project are routed to Salesforce Lead, preserving their source and activity history. Conversely, contacts that have an active, won, or completed project are mapped to Salesforce Contact, allowing them to retain account relationships, open opportunities, and related tasks duplication.

Followup CRM companies map directly to Salesforce Accounts on a one‑to‑one basis. When a company has sub‑companies in Followup CRM, the hierarchy translates to the ParentId field on the Salesforce Account, preserving the structure. For contacts associated with multiple companies, we assign one primary AccountId as the main relationship and create Account Contact Relation records for each secondary company, ensuring all affiliations are retained without duplicating the contact.

Followup CRM projects serve as the deal‑tracking entity and map to Salesforce Opportunities. The project name becomes the Opportunity Name, the project amount populates Opportunity Amount, and the project’s close date maps to CloseDate. Pipeline or status in Followup CRM determines Opportunity Stage via a value‑mapping table that aligns each Followup CRM status with the corresponding Salesforce stage. Probability and record type values are mapped to preserve the deal lifecycle.

Followup CRM milestones have no native counterpart in Salesforce, so we adopt a dual‑track migration strategy. Each milestone becomes a Salesforce Task linked to the parent Opportunity via WhatId, preserving milestone history. In addition, we create custom fields on the Opportunity—such as Milestone_1_Name__c, Milestone_1_Date__c, and subsequent numbered fields—for at‑a‑glance visibility without opening the related task list. This approach keeps milestone context accessible while respecting Salesforce’s object model.

Followup CRM goals—such as bid‑volume targets, revenue targets, or other performance metrics—have no direct Salesforce counterpart. We preserve these values by creating custom fields on the Opportunity object: Goal_Type__c (a pick‑list) holds the goal name, and Target_Amount__c (currency or number) stores the numeric target. This mapping keeps reporting continuity after cutover, allowing sales teams to compare historical goal performance against actual Opportunity results within Salesforce dashboards and reports.

Followup CRM tasks map one‑to‑one to Salesforce Tasks, preserving the core task details. The Subject field copies directly, while Status, Priority, and Due Date transfer unchanged. The related entity—whether a Contact, Company, or Project—maps to the appropriate WhoId or WhatId, ensuring task context stays linked to the originating record.

Followup CRM notes are migrated to Salesforce’s modern Notes object, not the legacy Note entity. During the migration, rich‑text formatting—including bold, bullet lists, hyperlinks, and embedded images—is preserved so the content looks the same in Salesforce as it did in Followup CRM. Each note is attached to its parent record (Contact, Account, or Opportunity) using the ParentId lookup, ensuring that note context is visible when viewing the related Salesforce record.

Followup CRM file attachments are uploaded to Salesforce using the ContentDocument/ContentVersion model. Each file is linked to its parent record (Contact, Account, Opportunity, etc.) via a ContentDocumentLink entry. Salesforce enforces a 25 MB per‑file size limit; any attachment exceeding this threshold is flagged in the audit and reported to your admin for a decision—whether to split the file, store it externally with a reference URL, or exclude it from migration.

Followup CRM users are matched to Salesforce Users by email address. Unmatched owners are flagged before migration — your team either invites them to Salesforce first or assigns their records to a fallback owner. No record lands in Salesforce without a resolved OwnerId.

Followup CRM custom properties on projects are translated into Salesforce custom fields on the Opportunity object. We assign the __c suffix to each API name, select the appropriate field type (text, pick‑list, number, date, etc.), and map the original values so they appear in Salesforce as they did in Followup CRM. During the migration run, data loads populate these custom fields automatically, preserving historical project metadata for reporting and validation.

Followup CRM custom properties defined on contacts become Salesforce custom fields on the Contact object. We add the __c suffix to the API name, set the correct field type (text, number, date, pick‑list, etc.), and load the original values during migration. For pick‑list fields, each Followup CRM option maps to the matching Salesforce pick‑list value, preserving dropdown selections and avoiding validation errors.

Followup CRM workflows and automation rules cannot migrate to Salesforce Flow. We export your workflow definitions as a structured document (trigger events, conditions, actions) that your Salesforce admin can use as a rebuild reference in Flow Builder or Process Builder.