Migrate from FreeCRM to Salesforce Sales Cloud

FreeCRM Contact records map to Salesforce Contact when they have a valid company association and the customer defines them as qualified buyers. FreeCRM Contacts that represent unqualified prospects (no assigned deal, no company link) map to Salesforce Lead. We apply the split rule during scoping based on the customer's business logic and preserve the original FreeCRM contact record type in a custom field freecrm_original_type__c for reconciliation. Email, phone, address, and name fields map 1:1.

FreeCRM Company records map directly to Salesforce Account. Company name becomes Account Name, domain becomes Website, and industry becomes Industry picklist where the FreeCRM template exposes it. The Account is created before any Contact import so that AccountId is available for the Contact-to-Account lookup at insert time.

FreeCRM Lead records (when the template exposes a separate Lead object) map to Salesforce Lead. FreeCRM's template-driven lead status field maps to Salesforce Lead Status, and lead source maps to LeadSource. Any FreeCRM custom fields on Lead (defined via template) are inventoried during discovery and mapped to Salesforce custom fields (freecrm_custom_field__c naming convention) that we provision before migration.

FreeCRM Deal records map to Salesforce Opportunity. Deal name becomes Opportunity Name, amount maps to Amount, expected close date maps to CloseDate, and stage (stored as free text in FreeCRM) maps to the StageName value that we configure as part of the Salesforce Sales Process setup. We preserve FreeCRM deal notes in a custom field freecrm_deal_notes__c on Opportunity.

FreeCRM stores pipeline stages as account-defined text values on the Kanban board. We extract the full stage list during discovery and create a corresponding Salesforce Sales Process with matching stage names and probabilities. Each stage gets a Loss Reason or Win Reason field only if FreeCRM exposed this data in a custom template field.

FreeCRM template fields vary per account and are the primary migration risk. We inventory every template in use during discovery, extract the complete field set across all record types, map each to a typed Salesforce custom field, and provision the schema in Salesforce before any data import. Any template field without a clear Salesforce equivalent is flagged for the customer's admin to define during scoping.

FreeCRM task records (follow-up reminders, to-dos) map to Salesforce Task. Subject maps to Subject, due date maps to ActivityDate, status maps to Status, and priority maps to Priority. Owner assignment resolves via email match to the Salesforce User table.

FreeCRM event records (meetings, calls) map to Salesforce Event. Start time and end time map to StartDateTime and EndDateTime, location maps to Location, and description maps to Description. Attendee resolution links EventRelation records to the migrated Contact or Lead.

FreeCRM exports tags as comma-separated values on Contact and Company records. We split these into array values and map them to Salesforce multi-select picklist fields on the Contact or Account. We recommend the customer define the multi-select field during scoping to capture the tag vocabulary.

FreeCRM Owner assignments on records resolve by email match to the Salesforce User table. Any FreeCRM user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision. OwnerId is required on Opportunity and Contact, so this step gates the migration.

FreeCRM Pro invoice records (line items, totals, status) map to a Salesforce custom object we provision during schema setup (Invoice__c) with line item child records (Invoice_Line_Item__c). Invoice number, date, total, and status map directly. FreeCRM Pro storage and campaign data are only migratable if the account is on the Pro tier; we confirm tier status during scoping.

FreeCRM file attachments on records (contacts, companies, deals) map to Salesforce ContentDocument and ContentDocumentLink. We extract attachments from the CSV export package, upload to Salesforce Files, and link to the parent record via ContentDocumentLink. Attachment-heavy accounts on the Free tier may hit undocumented storage limits during export; we confirm available headroom before initiating extraction.