Migrate from FIVE CRM to Salesforce Sales Cloud

FIVE CRM Contacts map directly to Salesforce Contact. We resolve the parent Account by matching FIVE CRM's Company association to a Salesforce Account name lookup, or by creating Account records from FIVE CRM Companies before Contact import. Email, phone, address, owner assignment, and all standard fields transfer cleanly via CSV or API. Every custom field requires explicit type confirmation during pre-migration field inventory because FIVE CRM does not expose schema via its public API.

FIVE CRM separates Leads from Contacts in its data model. We assess each Lead record's qualification status and source workflow at migration time: leads sourced through telemarketing campaigns and not yet worked map to Salesforce Lead; leads that have been contacted, qualified, and assigned to a sales rep map to Salesforce Contact with a parent Account. The original FIVE CRM lead_source field is preserved as a custom field lead_source__c on both Lead and Contact for attribution and reporting continuity.

FIVE CRM Companies map directly to Salesforce Account. We import Account before Contact to satisfy the AccountId lookup at the moment of Contact insert. Company name is the dedupe key; we flag any duplicates in the FIVE CRM export for the customer's admin to resolve before import because Salesforce requires unique Account names per org.

FIVE CRM pipelines and their custom stage names vary by tenant configuration. Each FIVE CRM pipeline maps to a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists only the migrated stage values. We rename any custom stage labels at the destination during import so the pipeline's business logic is preserved exactly. Stage probability percentages are mapped to StageProbability fields on each stage.

FIVE CRM Campaigns track email marketing sequences and engagement data. We migrate Campaign records and CampaignMember records linking each FIVE CRM Contact or Lead to the destination Campaign. Campaign status (Active, Planning, Completed) maps to Salesforce Campaign Status. Note that FIVE CRM's per-event email engagement logs (opens, clicks, replies) are not exposed via bulk export; we migrate campaign membership and contact-level engagement flags as custom fields on CampaignMember but do not transfer granular event timelines in a single migration pass.

FIVE CRM Tasks include due dates, assignees, completion status, and task type. We map tasks to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving FIVE CRM's owner reference to Salesforce OwnerId via the User mapping. FIVE CRM task types that are telemarketing-specific (call queue assignments, dial attempts) are mapped to custom Task fields or retained as a custom field for the customer's admin to decide on categorization post-migration.

FIVE CRM relies heavily on custom fields to support telemarketing-specific workflows including lead scoring, dial status tracking, and campaign tagging. We treat every custom field as requiring explicit field-level mapping during migration scoping: we enumerate all custom fields in use, confirm data type by querying the export endpoint directly (not relying on UI error output), and agree on a Salesforce destination before any data moves. FIVE CRM does not expose a complete schema document so this step is mandatory for every tenant. Skipping this inventory leads to silent type coercion or dropped values at the destination.

File attachments associated with Contacts, Companies, or Pipelines in FIVE CRM migrate via ContentDocument and ContentDocumentLink. We re-upload files where the original attachment URL is not accessible, and flag any attachment over 10MB for separate handling because Salesforce API size limits require chunked upload or a different delivery mechanism for large files.

FIVE CRM tags label records for segmentation and campaign targeting. Multi-value tags stored as comma-separated properties migrate to Salesforce multi-select picklist fields. Tags used for content classification migrate to Salesforce Topics with TopicAssignment records. The customer chooses tag strategy during scoping; if tags represent lead scoring tiers, they migrate as a custom numeric field on Lead or Contact.

FIVE CRM User records include names, roles, and assignment permissions. We map users to Salesforce User by email match. Any FIVE CRM user without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes because OwnerId is required on most standard Salesforce objects.

FIVE CRM tracks outbound calls with disposition, duration, and recording reference. We map these to Salesforce Task with TaskSubtype=Call, CallDisposition, and CallDurationInSeconds preserved. Call recordings transfer as ContentDocument records linked to the Task via ContentDocumentLink.

FIVE CRM email engagements migrate to Salesforce EmailMessage records (the email content) linked to a Task record (the activity timeline entry). The WhoId on Task points to the migrated Lead or Contact; WhatId points to the related Opportunity or Account. Email subject, body, and direction (inbound/outbound) are preserved. FIVE CRM does not expose per-event email engagement logs (open timestamps, click URLs) via bulk export; these are not migrated in this pass.