Migrate from FowCRM to Salesforce Sales Cloud

FowCRM Accounts map directly to Salesforce Account. We export all standard fields (Name, Industry, Website, Phone, Address) and custom properties attached to the Account Model via the two-step /Models and /Fields API discovery process. The FowCRM account name becomes the Account Name in Salesforce and serves as the dedupe key during import. Account is created first in the migration sequence so that Contact imports can resolve AccountId lookups immediately.

FowCRM Contacts map to Salesforce Contact with a required link to an Account. We export Contact fields, lifecycle stages, and custom properties, then re-link them to destination Accounts during import using AccountName as the lookup resolution key. Any Contact without a matching AccountName in the destination is held in a reconciliation queue until the Account is available or a new Account is created.

FowCRM Deals map to Salesforce Opportunity. The Deal stage property maps to Salesforce StageName via the pipeline-stage mapping table we build during scoping. Owner assignments migrate by resolving FowCRM owner_id to Salesforce OwnerId via the User email match. Closed-Won and Closed-Lost deal states preserve any custom reason or notes fields as Salesforce Loss Reason or custom Opportunity fields.

FowCRM Pipelines with configurable stages and probability percentages map to Salesforce Record Types on Opportunity, each paired with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from FowCRM to Salesforce StageProbability rounded to the nearest integer. We configure this in a Salesforce Sandbox before production migration to validate stage ordering.

FowCRM Case Management (available on Professional and Enterprise tiers only) maps to Salesforce Case. Case status, priority, and custom case-type fields from FowCRM require mapping to Salesforce Case Status, Priority, and custom picklist fields. We confirm the FowCRM plan tier during discovery — if the source is on Standard, the Cases API returns 403 and we skip this object gracefully rather than failing. Cases without an associated Account or Contact are linked to the parent Account by case-account reference before import.

FowCRM Survey definitions and response data are exported as structured JSON. Survey question schemas differ significantly between platforms, so we treat Survey data as a mapping exercise: we deliver survey questions as a written inventory with destination field recommendations, and survey responses as JSON blobs stored in a Salesforce custom object (Survey_Response__c) with a ContentVersion attachment for the raw response payload. This preserves the data without forcing a schema mismatch.

FowCRM Custom Fields are defined per Model, requiring a two-step discovery process that we handle explicitly. First, we enumerate all Models via /Models to build the complete model-to-field index. Second, we query /Fields for each Model ID to retrieve all custom field definitions including field type, label, and API name. Field types — picklist, text, date, number, boolean — are matched to equivalent Salesforce field types during schema design. Custom field values export alongside their parent records in the same migration batch to avoid orphaned custom property data.

FowCRM Activity records — calls, emails, meetings, and notes linked to Contacts or Accounts — export with their association metadata. Calls migrate as Task with TaskSubtype=Call; emails as EmailMessage linked to an Activity Task; meetings as Event with StartDateTime and EndDateTime preserved; notes as Salesforce Note or ContentNote (Lightning Experience) linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. The activity-to-record association uses the FowCRM reference ID resolved against the migrated Contact or Account to avoid orphaned timeline entries.

FowCRM User records including email, role, and department export for owner assignment purposes. We match FowCRM owners by email against the destination Salesforce org's User table. Any FowCRM owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. We recommend a pre-migration user alignment session to map FowCRM roles to Salesforce profiles and permission sets.

FowCRM offers industry-specific solution variants with pre-configured data models for verticals like field-service or retail. We detect which industry modules are active in the export scope and map their data to either Salesforce custom objects (for non-standard entities) or standard objects with a Record Type and custom fields (for entities that map to standard Salesforce objects like Cases or Contacts). The mapping strategy is decided during discovery based on the vertical module schema.

FowCRM integration configurations and webhook subscriptions are not exposed via the public API. We do not migrate these as they require manual reconfiguration in Salesforce. We deliver a written inventory of detected webhook endpoints and integration configurations (based on API discovery) for the customer's admin to reconfigure in Salesforce as Flows, Outbound Messages, Platform Events, or third-party integration apps post-migration.

If FowCRM holds Product records (used in Deal line items), they map to Salesforce Product2 with Standard Price Book entries created during import. ProductCode maps from any FowCRM SKU field. Pricebook2 assignment is resolved at migration time so that OpportunityLineItems can reference the correct pricebook during import.