CRM migration

Migrate from Funnel Leasing to Freshsales

Field-level mapping, validation, and rollback between Funnel Leasing and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Funnel Leasing logo

Funnel Leasing

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

12 of 13

objects map 1:1 between Funnel Leasing and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Funnel Leasing operates as a renter-centric CRM purpose-built for multifamily operators, organizing data around a unified guest card that spans inquiry through renewal. Freshsales uses the standard CRM object model: Leads, Contacts, Accounts, Deals, and Activities. The migration maps Funnel's Prospects to Freshsales Leads, Funnel's Property portfolios to Freshsales Accounts (with custom fields for unit counts and lease terms), and Funnel's communication logs to Freshsales Tasks and Events. The most significant structural difference is Funnel's lease object — no native Freshsales equivalent exists, so active lease terms, rent amounts, and lease dates migrate as custom fields on the linked Account or Deal record. We use Funnel's Customer API and Partner API endpoints to extract records, then load into Freshsales via its REST API with bulk operations for large record sets. Workflows, AI routing rules, and property-specific automation logic do not migrate and must be rebuilt in Freshsales. Our approach runs a sample migration first with field-level diff before committing the full data set.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Funnel Leasing logo

Funnel Leasing

What's pushing teams away

  • Enterprise pricing lacks transparency, requiring a sales conversation with no published pricing for the Full Funnel tier, making budget forecasting difficult for large portfolios.
  • Third-party BI integrations like Tableau and Snowflake are not included in base pricing and add significant cost, frustrating data teams that need native analytics.
  • Operators with highly differentiated property types or small portfolios report that the centralized model works best for uniform mid-to-large portfolios and can be overkill for niche operators.
  • Support model changes over time have frustrated some customers who report reduced support access compared to earlier pricing tiers, particularly for mid-market accounts.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Funnel Leasing objects map to Freshsales

Each row shows how a Funnel Leasing 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.

Funnel Leasing

Prospect

maps to

Freshsales

Lead

1:1
Fully supported

Funnel Prospects map 1:1 to Freshsales Leads. Funnel stores name, email, phone, source channel, and lifecycle stage on the prospect. Freshsales Lead object receives these directly. Owner resolution occurs by email match against Freshsales users. If a prospect's email matches an existing Freshsales user, the record assigns to that user; otherwise a fallback owner is used.

Funnel Leasing

Prospect (converted)

maps to

Freshsales

Contact + Account

many:1
Fully supported

Funnel Prospects that progressed to applied or lease-signed status become Freshsales Contacts linked to Accounts. Funnel's renter lifecycle stage determines which status values map to the Freshsales lead_status pick-list. Application status values require value-mapping in the migration plan. We verify each mapping against a sample before full execution.

Funnel Leasing

Property

maps to

Freshsales

Account

1:1
Fully supported

Funnel Property records map to Freshsales Accounts. Property name becomes Account Name. Address fields map to Billing Address on the Account. Funnel's property-level custom fields (e.g., unit count, property type) migrate as custom fields on the Account. We also ensure the country and time zone settings align for accurate reporting.

Funnel Leasing

Unit

maps to

Freshsales

Custom Field on Account

1:1
Fully supported

Funnel Unit records (individual apartment homes) have no direct Freshsales equivalent. Unit details — number, bedrooms, bathrooms, market rent — store as a JSON blob or repeating custom fields on the parent Property Account. FlitStack surfaces this in the migration plan and your admin decides the preferred schema.

Funnel Leasing

Lease

maps to

Freshsales

Deal + Custom Fields on Account

1:1
Fully supported

Funnel Lease records carry rent amount, lease start/end dates, security deposit, and unit assignment. Freshsales has no lease object. Active leases migrate as custom fields on the linked Account; if the team manages renewals as pipeline Deals, lease terms also populate Deal custom fields. Your admin chooses the target based on renewal workflow design.

Funnel Leasing

Appointment / Tour

maps to

Freshsales

Event

1:1
Fully supported

Funnel tour and appointment records map to Freshsales Events. Start time, end time, attendee status, and assigned agent migrate. Funnel's self-scheduled vs. agent-guided distinction stores as a custom Event field in Freshsales. Original scheduling timestamps and owner IDs preserved. If the tour is cancelled, we flag the Event status accordingly to maintain accurate calendars.

Funnel Leasing

Email / Text / Call

maps to

Freshsales

Task

1:1
Fully supported

Funnel omnichannel communications (email, SMS, phone call) all map to Freshsales Tasks. Communication type stored in the Task Type pick-list. Full message body or call notes migrate to Task description. Parent record link (prospect or property) preserved so the activity ties to the correct Freshsales Contact or Account.

Funnel Leasing

Task (internal)

maps to

Freshsales

Task

1:1
Fully supported

Funnel internal tasks assigned to leasing agents migrate as Freshsales Tasks. Due date, priority, status, and assigned owner map directly. Owner resolved by email match against Freshsales users. Unresolved Funnel tasks flagged before migration so no action items are silently dropped.

Funnel Leasing

Note

maps to

Freshsales

Note

1:1
Fully supported

Funnel notes attached to prospects or properties migrate to Freshsales Notes linked to the corresponding Contact or Account. Rich-text formatting preserved where Funnel's API returns HTML content. Author and create timestamp migrate for audit continuity. We also verify that any embedded images or attachments in notes are correctly transferred to Freshsales.

Funnel Leasing

Attachment / File

maps to

Freshsales

File

1:1
Fully supported

Files attached to Funnel records (e.g., ID documents, lease PDFs) download from Funnel storage and re-upload to Freshsales Files attached to the corresponding record. File size limits per Freshsales plan apply — large files may require chunking or a separate document storage reference.

Funnel Leasing

Tag

maps to

Freshsales

Tag

1:1
Fully supported

Funnel tags on prospects, properties, or leases migrate as Freshsales Tags. Tags are flat in both systems so no transformation required. Tags used for audience segmentation in Funnel transfer as reference data for Freshsales workflow rebuilding. We recommend reviewing tag usage after migration to align with new Freshsales segmentation needs.

Funnel Leasing

Custom Property

maps to

Freshsales

Custom Field

1:1
Fully supported

Funnel custom properties on any object (prospect, property, lease) require Freshsales custom fields. Data type mapping: text to text, number to number, date to date, pick-list to pick-list. Funnel pick-list values map value-by-value to Freshsales pick-list options. Custom field creation is a pre-migration step coordinated with your Freshsales admin.

Funnel Leasing

User / Owner

maps to

Freshsales

User

1:1
Fully supported

Funnel users and owners resolve to Freshsales users by email address. If a Funnel user has no matching Freshsales user, their records assign to a fallback owner or queue specified by your admin before migration runs. Funnel user role and permissions do not migrate — Freshsales profile and permission set assignment is a separate admin configuration step.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Funnel Leasing logo

Funnel Leasing gotchas

Medium

Funnel is not a party to rental transactions

Medium

PMS integration fees are bundled into per-unit pricing

High

No publicly documented bulk export API for large portfolios

Low

AI-generated fields are proprietary and may not map directly to destination fields

Medium

ResApp resident portal accounts are not migratable

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Lease records have no native Freshsales home — custom field design required before migration

    Funnel Leasing stores active lease terms, rent amounts, and deposit values as structured records. Freshsales has no lease object. We map lease data to custom fields on the Account record (for property-level lease tracking) and optionally to Deal custom fields (for renewal pipeline management). If your team tracks multiple units per renter, the migration plan needs a custom schema design session before data moves. Skipping this step results in orphaned lease fields or lost rent data on the destination side.

  • Funnel's renter-centric guest card collapses into separate Lead and Contact objects in Freshsales

    Funnel's unified guest card tracks a renter from first inquiry through lease signing and renewal in one profile. Freshsales splits this into Lead (unconverted prospects) and Contact (converted renters). Funnel lifecycle stage values map to Freshsales lead_status and Contact status fields, but the one-to-one guest card relationship does not translate directly. We handle the split during migration based on Funnel's status value, but ongoing renter lifecycle tracking after migration requires Freshsales workflow configuration to update Contact status as the relationship evolves.

  • Funnel's omnichannel communications require拆解 into separate Freshsales Task types

    Funnel logs email, SMS, phone call, and chat under a single communication stream on the guest card. Freshsales uses separate Task types for each channel, and built-in SMS and phone require Pro plan or higher. Funnel communications migrate as Freshsales Tasks with the communication type stored in Task Type. If your Freshsales plan is Growth ($9/user/month), built-in telephony is not included — SMS and call logs land as Tasks but the native Freshsales phone interface is unavailable without upgrading.

  • API rate limits constrain migration window for large Funnel instances

    Funnel Leasing's Customer API and Partner API apply rate limits per authenticated connection. Freshsales REST API also enforces per-plan rate limits (Growth: 500 requests per minute). Large migrations — particularly those pulling communication history across thousands of records — may require staggered API calls and batch processing. We handle rate-limit backoff automatically, but a large portfolio with dense communication logs can extend the migration clock by 24–48 hours beyond initial estimates.

  • Workflows, AI routing rules, and chatbot logic are not accessible via Funnel API

    Funnel Leasing's AI-driven leasing workflows, automatic lead routing rules, Prospect AI and Resident AI automation, and chatbot configurations are platform-internal and not exportable via the API. These cannot migrate. We export workflow definitions as a rebuild reference document so your Freshsales admin can reconstruct routing logic in Freshsales workflows or Freddy AI sequences. The rebuild effort is proportional to workflow complexity — a single routing rule takes minutes; multi-step AI sequences may require a planning session.

Migration approach

Six steps for a successful Funnel Leasing to Freshsales data migration

  1. Audit Funnel data inventory and design Freshsales schema

    FlitStack AI pulls a full inventory from Funnel Leasing's Customer API and Partner API — prospects, properties, units, leases, communications, tasks, notes, and files. We assess record counts, custom property definitions, and communication volume. Simultaneously, we review your Freshsales plan tier to confirm which objects, custom fields, and telephony features are available. We then deliver a Freshsales schema setup plan: Account custom fields for lease data, pipeline configuration for renewal Deals, and lead status value-mapping before any data moves.

  2. Resolve owners by email and flag unmapped users

    Funnel user and owner records are matched to Freshsales users by email address. Any Funnel owner without a corresponding Freshworks user account is flagged before migration begins. Your team either creates the Freshsales user first or designates a fallback owner (a queue or admin user) that receives those records. No record migrates without a resolved owner — this prevents orphaned data in Freshsales after go-live.

  3. Migrate accounts and properties before prospects and contacts

    Freshsales requires Account records to exist before Contacts can link to them via the AccountId lookup. We sequence the migration: Properties → Accounts first (with custom lease fields reserved), then Prospects → Leads (split by Funnel status), then converted renters → Contacts linked to their Account. Lease records land on the Account after the account exists. Communication history follows, tied to the parent Contact or Prospect record.

  4. Run sample migration with field-level diff

    A representative slice — typically 100–500 records spanning prospects across lifecycle stages, a sample property portfolio, active leases, and a mix of communication types — migrates first. We generate a field-level diff report comparing source values against Freshsales field values so you can verify lease date mapping, owner resolution, and communication type classification before the full run. You approve the sample before we commit to the full migration.

  5. Execute full migration with delta-pickup window and rollback plan

    Full data migration runs against Freshsales via bulk API operations. A delta-pickup window (typically 24–48 hours) captures any new prospects, updated lease statuses, or new communications created in Funnel during the cutover period. Every operation is logged in the FlitStack audit trail. If reconciliation reveals a mapping error, one-click rollback reverts Freshsales to its pre-migration state so the migration can re-run with corrected logic.

Platform deep dives

Context on both ends of the pair

Funnel Leasing logo

Funnel Leasing

Source

Strengths

  • AI-powered leasing automation embedded natively without requiring separate AI tool subscriptions
  • Transparent per-unit pricing model with published rates on Essentials and Intelligence tiers
  • Renter-centric data architecture gives a single view of each prospect and resident across the entire portfolio
  • Omnichannel communication logging unifies emails, calls, texts, and chats into one contact profile
  • Claims 70% faster approval-to-lease distribution through integrated online leasing workflows

Weaknesses

  • Enterprise pricing requires a sales conversation with no published Full Funnel tier rates
  • Third-party BI tool integrations (Tableau, Snowflake) incur additional costs not included in base pricing
  • Centralized portfolio-wide model may be unnecessarily complex for small or niche portfolios
  • API documentation is not publicly indexed at scale, requiring developer account access for schema reference
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Funnel Leasing and Freshsales.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Funnel Leasing: Not publicly documented..

  • Data volume sensitivity

    B

    Funnel Leasing doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Funnel Leasing to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Funnel Leasing to Freshsales data migrations

Answers to the questions buyers ask most during Funnel Leasing to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Funnel Leasing to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Funnel-to-Freshsales migrations complete in 48–72 hours for under 50,000 records. Larger portfolios with 100,000+ records or complex lease-data custom field setups extend to 5–10 days. The longest phase is Freshsales schema design (custom fields, pipeline configuration, value mapping) before data moves — typically 3–5 business days of planning with your admin. During schema design, we also configure any required custom pick-lists, verify API rate limits, and align owner assignments across the new environment.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Funnel Leasing.
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day