Migrate from Friday CRM to Salesforce Sales Cloud

Friday CRM Company records map directly to Salesforce Account. The Company name becomes Account Name; the domain or website stored in Friday becomes the Account Website field. We use Company Name as the dedupe key during import to prevent duplicate Account creation. Account is inserted before Contact import so that the AccountId lookup relationship is satisfied at Contact insert time. If the customer uses Friday CRM's industry or address fields, those map to Industry and BillingAddress on Account.

Friday CRM Contacts with no associated Deal or with early-stage status map to Salesforce Lead. Contacts with active Deals or explicit customer status map to Salesforce Contact attached to the Account derived from the associated Friday CRM Company. We define the split rule during scoping based on the customer's data — for example, Contacts linked to Deals with stage values above a defined threshold become Contacts; all others become Leads. The original Friday CRM contact record ID is preserved in a custom field friday_contact_id__c on both Lead and Contact for reconciliation.

Friday CRM Contacts that qualify as customers (active Deal, past Deal, or explicitly tagged) map to Salesforce Contact records linked to the Account from the associated Company. Standard contact fields — FirstName, LastName, Email, Phone, Title — map directly. Custom contact fields from Friday CRM undergo type mapping: radio selects become picklists, multiple checkboxes expand to individual checkbox fields or a multi-select picklist depending on the destination field count, and URL fields map to Salesforce URL fields.

Friday CRM Deals map to Salesforce Opportunity records. The Deal value maps to Amount; Deal stage maps to StageName via the configured Sales Process; Deal name maps to Opportunity Name. If the Deal is linked to a Contact and Company in Friday, we resolve AccountId and ContactId at migration time. Pipeline stage ordering from Friday's Kanban board maps to the Salesforce stage sequence defined in the corresponding Sales Process. Closed-Lost and Closed-Won statuses from Friday become Salesforce Stage values that match the customer's configured stage set.

Friday CRM's customizable stage names and ordering are preserved in Salesforce as StageName values within a Sales Process. We create a Salesforce Record Type for the Opportunity and configure a Sales Process that whitelists only the stages present in the customer's Friday CRM pipeline. Probability percentages from Friday's stage settings migrate to StageProbability on each stage. If Friday CRM used weighted pipeline values, those recalculate in Salesforce's standard pipeline analytics.

Friday CRM's single Kanban pipeline maps to one Salesforce Opportunity Record Type with one Sales Process. If the customer uses multiple parallel pipelines (available in Friday CRM's settings), each becomes a separate Salesforce Record Type. Record Type assignment determines which Page Layout and stage set the Opportunity uses. We configure this in the destination org before any Opportunity records are inserted.

Friday CRM custom fields defined on the Company object migrate to custom fields on the Salesforce Account object. We perform type mapping during the field audit phase: radio select becomes picklist with the same option values; multiple checkboxes may expand to multiple checkbox fields or consolidate into a multi-select picklist if the customer prefers fewer fields; date and URL fields map directly to Salesforce Date and URL types. The customer approves the type mapping before any Account records are imported.

Friday CRM custom fields defined on Contact migrate to Salesforce Contact custom fields following the same type-mapping rules: radio select to picklist, multiple checkboxes to multi-select picklist or individual boolean fields, single checkbox to checkbox. Text, number, date, URL, and multi-line fields map directly. Custom field labels from Friday CRM are preserved as Salesforce field labels, with API names generated by converting to Pascal case and appending __c.

Friday CRM custom fields defined on Deal migrate to Salesforce Opportunity custom fields using the same type-mapping rules as Contact and Company. If Friday CRM stored product or SKU information in Deal custom fields, we evaluate whether those map to Salesforce Product2 and OpportunityLineItem objects instead, depending on whether the customer is implementing product-level quoting in Salesforce.

Friday CRM notes linked to Contacts or Deals migrate to Salesforce Note records attached via ContentDocumentLink to the parent Contact or Opportunity. Note body text and creation timestamp are preserved. If Friday CRM records store call logs or meeting outcomes as activities rather than notes, those migrate as Task records with TaskSubtype set appropriately. Activity timestamps are preserved as ActivityDate on the Task. We audit the Friday CRM export to confirm which object holds activity history before finalizing the mapping.

Friday CRM tags applied to Contacts and Deals appear as comma-separated values in the export. We parse, deduplicate, and normalize the tag set. Tags with fewer than 15 unique values migrate to a Salesforce multi-select picklist on the relevant object. Tags with more than 15 values migrate to Salesforce Topics with TopicAssignment records linked to the parent record. The customer chooses the strategy during scoping.

Friday CRM does not expose owner IDs in the CSV export directly. We derive owner references from the record's last-modified-by metadata or by matching contact owner email addresses to Salesforce User records. Any Friday CRM owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId on Opportunity and Contact resolves at migration time via email lookup.

Friday CRM does not expose file attachments in its documented CSV export or public API. Attachments uploaded to Companies, Contacts, or Deals cannot be retrieved programmatically. We flag this limitation in the discovery phase and recommend that the customer exports attachments manually through Friday CRM's UI before the migration date. Migrated records will not have file attachments; these must be re-uploaded to Salesforce after cutover.

Friday CRM's native OAuth connections to Gmail, G Suite, Mailchimp, and RingCentral store credentials and tokens within the platform. These credentials are not part of the exportable data and cannot be transferred to Salesforce. Each integration must be reconfigured from scratch in Salesforce after migration, including re-authenticating OAuth connections, reconnecting Gmail sync settings, and rebuilding any automation rules that depended on those integrations. We document the full list of active integrations during discovery as a reconfiguration checklist.