Migrate from Getfly CRM to Salesforce Sales Cloud

Getfly Accounts hold both company-level data and person-level contact fields in a single object. We split at migration time using the Getfly account type or pipeline stage: accounts with no associated deal or with a 'prospect' stage map to Salesforce Lead; accounts with active deals or a 'customer' stage map to Salesforce Contact attached to a Salesforce Account. We preserve the original Getfly Account name, phone, email, and address fields in mapped Salesforce fields, and store a custom field getfly_original_id__c on both Lead and Contact for audit traceability.

Getfly Account records that represent companies (as distinguished from person-level accounts during the split) map to Salesforce Account. The Account Name, Website, Industry, and Billing Address migrate directly. We use the Account Name as the dedupe key during import. Salesforce Account must be created before any Contact import so that the AccountId lookup is satisfied at Contact insert time.

Getfly's configurable pipeline stages are account-specific with no published stage count ceiling. We extract the full stage list from the Getfly admin panel during discovery, map each stage to a Salesforce StageName value in a Salesforce Sales Process, and set StageProbability percentages matching the Getfly original. Each Getfly pipeline becomes a Salesforce Record Type on Opportunity.

Getfly Deals map to Salesforce Opportunity. The Getfly deal stage maps to the Salesforce StageName using the configured Sales Process. AccountId references are resolved using the Account mapping output. OwnerId is resolved via email-based user lookup. Closed-Lost and Closed-Won dates migrate to Salesforce CloseDate and IsClosed flags. Any Getfly custom fields on Deal (discount percentage, renewal date, custom flags) migrate to Salesforce Opportunity custom fields.

Getfly Products map to Salesforce Product2 records. The Getfly Product detail_custom_fields nested object is flattened into Salesforce custom fields on Product2, discovered by sampling records at export time (see custom field schema gotcha). ProductCode maps from Getfly sku. Standard Pricebook entries are created during import. The customer must enable a Pricebook on the Opportunity at the Salesforce admin level before Line Items import.

Getfly Activity records with type Task map to Salesforce Task. Activities with type Call map to Task with TaskSubtype = Call and CallDurationInSeconds in a custom field. Activities with type Meeting map to Salesforce Event with StartDateTime and EndDateTime preserved. All activity types link to the parent Contact or Account via the WhoId and WhatId Salesforce standard fields. We use the Salesforce Bulk API 2.0 for large activity volumes with batch sizes set to avoid API limit errors.

Getfly stores custom fields on Accounts and Products in detail_custom_fields nested objects. There is no published schema endpoint listing all active custom fields per account. We discover custom fields by sampling 50-100 Product records and 50-100 Account records at export time, then generate type-compatible Salesforce custom fields before import. We instruct customers to run a full custom field audit from the Getfly admin panel before migration kickoff to reduce the risk of missed fields.

Getfly Users act as record owners with name, email, and role. We export the full user roster and map OwnerId to Salesforce UserId using email as the dedupe key. Any Getfly Owner without a matching Salesforce User is held in a reconciliation queue. The customer's Salesforce admin provisions missing Users (active status matching whether the Getfly user is active) before record import resumes. Migration cannot proceed past owner resolution because Opportunity and Contact require a valid OwnerId.

Getfly Attachments are referenced by URL in the API. We download each file to local storage during export, preserving the original filename and MIME type, then re-upload to Salesforce as ContentVersion records linked via ContentDocumentLink to the parent Account, Contact, or Opportunity. File size limits follow Salesforce's 25 MB per ContentVersion ceiling. Files exceeding this threshold are flagged for the customer to store in an external file system with a link stored in Salesforce.

Getfly Campaigns track name, start/end dates, and linked accounts as member contacts. We map Campaigns to Salesforce Campaign and create CampaignMember records linking the Campaign to the migrated Contact or Lead. Campaign member status (active, opted-out, responded) migrates to Salesforce CampaignMember Status values. Historical campaign performance data (impressions, clicks, conversions) migrates to Salesforce Campaign custom fields if present in Getfly.

Getfly PABX call logs include call direction (inbound/outbound), duration, disposition, and a recording URL that may be a signed or time-limited link. We export call logs as Task records with TaskSubtype = Call, CallDurationInSeconds, and CallType (inbound/outbound) in Salesforce custom fields. We download recording files at export time and re-upload to Salesforce as ContentVersion records linked to the Task via ContentDocumentLink to prevent broken links. If the customer's PABX system changes at migration time, recording continuity is explicitly scoped in the discovery questionnaire.

Getfly Workflow rules are internal platform configuration with no public export endpoint. We do not migrate automations as code. We deliver a written inventory of every active Getfly Workflow during discovery, including trigger conditions, actions, delays, and recipient logic, with a recommended Salesforce Flow equivalent. The customer's Salesforce admin rebuilds these post-migration. This is scoped as a separate automation rebuild engagement outside the standard migration scope.