Migrate from Followup CRM to Freshsales

Followup CRM contacts map 1:1 to Freshsales Contacts. We preserve the original create date as a custom datetime field since Freshsales CreatedDate reflects migration time. Owner resolution happens by email match against Freshsales users — unmatched owners are flagged before migration commits any records.

Followup CRM stores lifecycle stages as a custom contact property. These values (Subscriber, Lead, MQL, SQL, Customer) map to Freshsales' native Contact Status pick-list. If Followup CRM uses custom stage names, we create a custom pick-list field and map each value explicitly during migration.

Followup CRM companies map directly to Freshsales Accounts. Address fields (street, city, state, zip, country) migrate to Freshsales' compound address field. If Followup CRM stores multiple addresses per company, the primary address migrates as Account.Address and secondary addresses surface as custom fields.

Followup CRM deals (including bid records) map to Freshsales Deals. The deal name, amount, stage, close date, and owner migrate directly. Followup CRM's construction-specific stage names (e.g., Bid Sent, Under Review, Won Job) map to Freshsales deal stage values — we create the Freshsales pipeline and stage values first, then map them during migration.

Followup CRM activities (calls, emails, meetings) map to Freshsales Sales Activities with original timestamps and owners preserved. Call logs, email records, and meeting records each carry their association to the parent Contact or Deal. Duration and outcome fields map to Freshsales activity properties where available.

Followup CRM notes migrate as Freshsales Notes linked to their parent Contact, Account, or Deal record. The note body maps to the Note content field with the original author and create date preserved. If Followup CRM notes contain attachments, those files are extracted, re-uploaded to Freshsales Files, and linked back to the parent Note record using Freshsales' file association mechanism.

Followup CRM custom objects map 1:1 to Freshsales custom objects. Custom object relationships that Followup CRM models as N:N require Freshsales junction objects or association fields. We document the relationship model during the audit phase and create Freshsales custom objects with the appropriate associations before migration.

Followup CRM tags migrate to Freshsales Tags. Tags are preserved on both Contact and Deal records. Freshsales Tags support multiple tags per record — we map each Followup CRM tag to a Freshsales tag value and resolve any duplicates during the field mapping phase.

Followup CRM users are resolved to Freshsales users by email address. Users that exist in Followup CRM but not in Freshsales are flagged during the audit phase — your team either provisions the user in Freshsales first or assigns a fallback owner for migration. Records without a resolvable owner are held in a queue rather than committed.

Followup CRM's goals and quota module has no Freshsales native equivalent. Team-level sales targets, bid volume goals, and quota metrics migrate as read-only custom fields on the Freshsales User record. This preserves the data for reference but does not replicate Followup CRM's active goal-tracking dashboards.

Followup CRM bid records carry construction-specific data — bid amount, bid status, bid type, estimated start date — that Freshsales Deal objects do not natively support. We create custom fields on the Freshsales Deal object (e.g., Bid_Amount__c, Bid_Status__c, Bid_Type__c) before migration and populate them from Followup CRM's bid record fields.

Followup CRM pipeline structure (construction stages, status order, probability weights) maps to Freshsales Pipelines and Stages. We create Freshsales pipelines matching Followup CRM's stage names, define probability and forecast category per stage, and map stage transitions. Followup CRM's stageentered timestamp is preserved as a custom datetime field on the Deal.