CRM migration
Field-level mapping, validation, and rollback between Real Intelligence and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Real Intelligence
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Real Intelligence and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Real Intelligence typically stores CRM data using a flat contact-and-deal model with limited pipeline branching. Freshsales uses a Lead-to-Contact-to-Account-to-Deal hierarchy with separate objects for each stage. The migration requires splitting merged contact-company records into proper Account lookups, mapping Real Intelligence deal stages to Freshsales pipeline stages, and resolving owner assignments by email match against Freshsales user accounts. Custom properties from Real Intelligence migrate as Freshsales custom fields on the equivalent object. Workflows, automation sequences, and email templates do not transfer — FlitStack AI exports workflow definitions as a rebuild reference for your Freshsales admin. The migration uses Freshsales Bulk API for leads, contacts, accounts, and deals, with standard API calls for custom objects and attachments. A 24–48 hour delta-pickup window captures any records modified during the cutover period. Freshsales Pro plan and above supports advanced lead scoring and territory management that may require Freshsales-side configuration after migration completes. Additionally, Real Intelligence record ownership metadata is preserved through email-based user matching, ensuring accountability and audit trails remain intact throughout the transition process.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Real Intelligence object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Real Intelligence
Contact
Freshsales
Contact
1:1Real Intelligence contacts migrate to Freshsales Contacts with direct field mapping. Email serves as the primary deduplication key. Contacts without a company association in Real Intelligence create standalone Freshsales Contacts with no AccountId link. All contact phone numbers, job titles, and address fields map directly to corresponding Freshsales Contact fields, preserving the complete contact profile during migration.
Real Intelligence
Contact (prospect status)
Freshsales
Lead
1:manyReal Intelligence records marked as prospects or unqualified contacts split to Freshsales Leads. Lead conversion in Freshsales creates Account, Contact, and optionally Deal records. The split preserves source lifecycle data in a custom field for reporting continuity. Lead status values map to Freshsales predefined statuses (New, Contacted, Qualified, Converted) with original values retained in a custom field for historical analysis.
Real Intelligence
Company
Freshsales
Account
1:1Real Intelligence company records map directly to Freshsales Accounts. Company hierarchy (parent-subsidiary relationships) migrate using Freshsales Parent Account field. Multi-company associations on Real Intelligence contacts surface as Freshsales Account Contact Relationships. Industry classification and employee count data transfer directly, with annual revenue preserved in the standard Freshsales Annual Revenue field.
Real Intelligence
Deal
Freshsales
Deal
1:1Real Intelligence deals map to Freshsales Deals with stage mapping validated against the target pipeline configuration. If Real Intelligence uses multiple deal stages beyond Freshsales default pipeline capacity, additional pipelines are created in Freshsales before migration. Deal amounts, close dates, and probability percentages transfer directly, with owner assignments resolved via email matching to Freshsales user accounts.
Real Intelligence
Pipeline
Freshsales
Pipeline
1:1Real Intelligence pipeline definitions become Freshsales Pipelines. Each pipeline in Real Intelligence requires a corresponding named pipeline in Freshsales. Pipeline stage order and probability values are mapped value-by-value during migration. Stage names are preserved as configured in Freshsales Admin, with probability weights applied from the source Real Intelligence pipeline definition.
Real Intelligence
Activity (calls, emails, meetings)
Freshsales
Sales Activities (Tasks, Appointments)
1:1Real Intelligence call logs migrate as Freshsales Tasks with Type='Call'. Email activities become Tasks with Type='Email'. Meeting records map to Freshsales Appointments preserving original start time, duration, and attendee data. Activity owner assignments resolve via email match to Freshsales users, with unresolved owners flagged for admin review.
Real Intelligence
Note
Freshsales
Note
1:1Notes migrate to Freshsales Notes attached to the parent record (Contact, Account, or Deal). Rich-text formatting in Real Intelligence notes is preserved. Notes created by specific users link to the corresponding Freshsales user where email-match succeeds. Attachments within notes are extracted and re-uploaded as separate Freshsales Files linked to the parent record.
Real Intelligence
Custom Property (Contact)
Freshsales
Custom Field (Contact)
1:1Real Intelligence custom contact properties become Freshsales Contact custom fields. Field type mapping converts pick-lists to Freshsales dropdown fields, date fields to date pickers, and numeric fields to number fields. Freshsales Enterprise plan required for advanced custom field types. Required field settings are preserved, and default values transfer where configured in Real Intelligence.
Real Intelligence
Custom Property (Deal)
Freshsales
Custom Field (Deal)
1:1Real Intelligence deal-level custom properties migrate as Freshsales Deal custom fields. Stage-related custom properties (e.g., probability overrides, custom milestone fields) map directly if Freshsales supports the field type, otherwise stored as text fields. Currency-formatted values convert to numeric fields with currency metadata preserved in Freshsales Deal Amount settings.
Real Intelligence
Product
Freshsales
Product
1:1Real Intelligence product catalog items map to Freshsales Products with SKU, pricing, and description fields preserved. Product associations on deals migrate as Deal Products linked to the migrated Product records. Product images stored in Real Intelligence upload to Freshsales Files and associate with the corresponding Product record.
Real Intelligence
User / Owner
Freshsales
User
1:1Real Intelligence user records are matched to Freshsales users by email address. Unmatched owners are flagged before migration commits — teams either invite the user to Freshsales first or assign records to a fallback owner designated by the admin. User role and permission settings require manual configuration in Freshsales Admin post-migration, as these are platform-specific security settings.
Real Intelligence
Attachment / File
Freshsales
File
1:1Real Intelligence file attachments re-upload to Freshsales Files attached to the parent record. File size limits apply — Freshsales supports up to 40MB per attachment. Inline images in notes are extracted and rehosted as separate file attachments. File metadata including original filename and upload timestamp are preserved in Freshsales File records.
| Real Intelligence | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Contact (prospect status) | Lead1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Activity (calls, emails, meetings) | Sales Activities (Tasks, Appointments)1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom Property (Contact) | Custom Field (Contact)1:1 | Fully supported | |
| Custom Property (Deal) | Custom Field (Deal)1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Attachment / File | File1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Real Intelligence gotchas
Salesforce dependency is a hard prerequisite for any Real Intelligence product
Custom CAD floor plan files require separate binary migration
Real Bots AI voice agent state is not exportable
MyQR app QR codes are tied to vendor infrastructure
Real Events QR scanner integration requires Salesforce mobile app or vendor-issued device
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit Real Intelligence data model and Freshsales target schema
FlitStack AI connects to Real Intelligence via API to enumerate all custom properties, pipeline configurations, user accounts, and relationship structures. Simultaneously, we inspect the target Freshsales account to identify existing custom fields, pipeline stages, and user list. The audit output is a gap analysis: which Real Intelligence fields have direct Freshsales equivalents, which require custom field creation, and which require transformation logic. This step typically takes 2–4 business days and requires read-only API credentials for both platforms.
Create Freshsales custom fields and pipelines
Based on the gap analysis, FlitStack AI generates a Freshsales setup specification: custom field definitions with correct types, pipeline names with stage configurations, and owner assignment rules. Your Freshsales admin creates these elements before the migration run. We provide step-by-step instructions and validate the setup via Freshsales API to confirm fields and pipelines exist before data movement begins. This step typically requires 1–3 days of Freshsales admin effort.
Run sample migration with field-level diff
A representative sample (typically 200–500 records spanning contacts, accounts, deals, and activities) migrates first. FlitStack AI generates a field-level diff comparing source values against destination values, identifying any mapping gaps or transformation errors. You review the diff and approve before the full migration commits. Sample migration plus review cycle takes 1–2 business days. Any mapping corrections are applied to the full migration configuration before the production run.
Execute full migration with delta-pickup window
Full data migration runs against Freshsales using Bulk API for standard objects and REST API for custom objects and attachments. A delta-pickup window (typically 24–48 hours) runs in parallel, capturing any Real Intelligence records modified during the cutover period. Audit logs record every record created, updated, or skipped. After migration completes, FlitStack AI generates a reconciliation report showing record counts by object, mapping success rates, and any records that require manual review.
Validate migration and provide rollback capability
Post-migration validation compares record counts and field completeness between Real Intelligence and Freshsales. FlitStack AI surfaces any discrepancies (duplicate detection, missing associations, owner resolution failures) for your team to resolve. One-click rollback is available within 48 hours of migration completion — this reverts the Freshsales instance to its pre-migration state if critical issues are discovered. After rollback window closes, the Freshsales instance is the active system of record and Real Intelligence can be decommissioned.
Platform deep dives
Real Intelligence
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Real Intelligence and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Real Intelligence: Inherits Salesforce API governor limits — typically 15,000 API calls per 24h for Enterprise Edition (varies by edition and add-on licensing)..
Data volume sensitivity
Real Intelligence exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Real Intelligence to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Real Intelligence to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Real Intelligence
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.