---
title: "LeadSimple to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate LeadSimple to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/leadsimple/to/hubspot"
---

# LeadSimple to HubSpot migration

Moving from LeadSimple to HubSpot means shifting from a property-management-focused CRM to a unified platform that handles marketing, sales, and service in one place. FlitStack AI maps every lead, contact, property, and custom field from LeadSimple into HubSpot's contact, company, deal, and custom-object model — preserving original create dates, stage history, and owner assignments so your HubSpot instance reflects the full picture of each prospect and customer from day one.

Short answer

FlitStack AI migrates contacts, custom object: properties, custom object: units, deal pipelines and deal stages from LeadSimple to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/leadsimple/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source LeadSimple ![](https://flitstack.ai/platforms-trim/leadsimple.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact Custom Object: Property Custom Object: Unit Deal Pipeline Deal Stage

Mapped field by field · sample run · one-click rollback

## What moves from LeadSimple to HubSpot?

LeadSimple is built around property management workflows — leads tied to properties, lease-management pipelines, and property-specific custom fields.

Read the full summary

HubSpot organizes data around contacts, companies, and deals with a general-purpose CRM model that supports marketing automation, sales pipelines, and service tickets. The migration carries LeadSimple's leads, contacts, property associations, pipeline stages, tasks, and custom fields into HubSpot's equivalent objects. The harder problems are mapping LeadSimple's property-centric data model to HubSpot's contact-and-company graph, preserving pipeline stage history in HubSpot's deal lifecycle, and handling LeadSimple's process-based automation logic that has no HubSpot equivalent. FlitStack AI uses LeadSimple's export API and CSV extraction to read all standard and custom fields, then maps them field-by-field into HubSpot via the Contacts API, Companies API, Deals API, and Custom Objects API. A sample migration with field-level diff runs first; the full migration follows with a 24-48 hour delta-pickup window. Workflows, sequences, and process automation must be rebuilt in HubSpot — we export the logic as a reference document for your admin.

direct

### Lead (LeadSimple) → Contact (HubSpot)

LeadSimple leads map to HubSpot contacts.

How it maps

The contact's name, email, phone, and address fields transfer directly. LeadSimple's 'Lead Name' field splits into HubSpot firstname and lastname properties. Original LeadSimple create date is preserved as a custom datetime field since HubSpot's Createdate is set at migration time.

custom\_field\_required

### Property (LeadSimple) → Custom Object: Property (HubSpot)

LeadSimple properties have no direct HubSpot equivalent — they become a HubSpot custom object named 'Property'.

How it maps

Property address, type, occupancy status, and number of units become custom properties on the Property custom object. Each LeadSimple property record creates one Property custom object record linked to its associated contact.

custom\_field\_required

### Unit (LeadSimple) → Custom Object: Unit (HubSpot)

LeadSimple units belong to properties and track occupancy, rent amount, and lease dates.

How it maps

Units map to a HubSpot custom object linked to the Property custom object via a custom association. Unit-level rent and lease-end dates become custom properties on the Unit custom object for reporting against deal pipelines.

transformed

### Pipeline (LeadSimple) → Deal Pipeline (HubSpot)

LeadSimple pipelines model property lifecycle stages — Inquiry, Showing, Application, Lease, Renewal.

How it maps

Each LeadSimple pipeline becomes a HubSpot deal pipeline. Stage names map value-by-value to HubSpot deal stages within each pipeline. Stage-entry timestamps are preserved as custom datetime fields on the deal record.

value\_mapping

### Stage Status (LeadSimple) → Deal Stage (HubSpot)

Stage status values (Active, Won, Lost, On Hold) map to HubSpot deal stages.

How it maps

LeadSimple's 'Closed At' timestamp maps to HubSpot's closedate. For deals where LeadSimple has no close date, HubSpot's close date defaults to the migration date — flagged for admin review.

custom\_field\_required

### Process (LeadSimple) → Custom Object: Process (HubSpot)

LeadSimple processes track property-management workflows like lease renewals and make-ready tasks.

How it maps

Processes map to a HubSpot custom object since HubSpot has no native process-tracking equivalent. Process stage, assigned user, and due date become custom properties. Process-task associations require a junction object in HubSpot.

******What moves 12 objects

LeadSimple HubSpot

- Lead Contact 1:1
- Property Custom Object: Property transformed
- Unit Custom Object: Unit transformed
- Pipeline Deal Pipeline transformed
- Stage Status Deal Stage transformed
- Process Custom Object: Process transformed

\+ 6 more in the mapping below

## How LeadSimple and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension             | LeadSimple                                                                                               | HubSpot                                                                                                      |
| --------------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Core focus            | LeadSimple is property-management-centric: leads and pipelines are tied to properties, leases, and units | HubSpot is general-purpose CRM: contacts and companies are central, deals and pipelines are sales-centric    |
| Pipeline model        | LeadSimple pipelines model lease-management stages (Inquiry, Showing, Application, Lease, Renewal)       | HubSpot deal pipelines model sales stages (Appointment, Proposal, Negotiation, Closed Won/Lost)              |
| Property data         | LeadSimple natively stores properties, units, and occupancy data as first-class objects                  | HubSpot has no native property object — these must become custom objects or deal-associated custom fields    |
| Custom fields         | LeadSimple custom fields exist on contacts, properties, units, and processes with conditional logic      | HubSpot custom properties exist on contacts, companies, deals, and custom objects with HubSpot's type system |
| Automation scope      | LeadSimple Autopilot runs property-specific triggers: lease renewals, make-readies, delinquencies        | HubSpot workflows run on CRM objects and marketing actions — property-specific triggers need custom rebuild  |
| Billing model         | LeadSimple charges per user per month plus per-door for Operations ($1.35/door/month)                    | HubSpot charges per user per month with marketing contacts billed separately above free limits               |
| Integration ecosystem | LeadSimple integrates with AppFolio and Buildium for property management sync                            | HubSpot has 1,000+ integrations via the App Marketplace and Salesforce connector for bi-directional sync     |

## LeadSimple to HubSpot field mapping

The 30 most-used fields of 32 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/leadsimple/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

LeadSimple HubSpot

1. `lead_name` Lead `firstname` Contact
2. `lead_name` Lead `lastname` Contact
3. `email_address` Lead `email` Contact
4. `combined_phone_numbers` Lead `phone` Contact
5. `tracked_phone_number` Lead `mobile` Contact

| LeadSimple field              | HubSpot field                      | Mapping                 | Note                                                                                                                                                                         |
| ----------------------------- | ---------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Lead.lead_name`              | `Contact.firstname`                | transformed             | LeadSimple Lead Name splits into HubSpot firstname and lastname. If Lead Name contains a single string, firstname gets the full name; lastname defaults to '(not provided)'. |
| `Lead.lead_name`              | `Contact.lastname`                 | transformed             | See firstname mapping. If LeadSimple stores first/last separately, they map directly to HubSpot firstname and lastname.                                                      |
| `Lead.email_address`          | `Contact.email`                    | direct                  |                                                                                                                                                                              |
| `Lead.combined_phone_numbers` | `Contact.phone`                    | direct                  |                                                                                                                                                                              |
| `Lead.tracked_phone_number`   | `Contact.mobile`                   | direct                  |                                                                                                                                                                              |
| `Lead.address`                | `Contact.address`                  | direct                  |                                                                                                                                                                              |
| `Lead.city`                   | `Contact.address.city`             | direct                  |                                                                                                                                                                              |
| `Lead.state`                  | `Contact.address.state`            | direct                  |                                                                                                                                                                              |
| `Lead.zip_code`               | `Contact.address.zip`              | direct                  |                                                                                                                                                                              |
| `Lead.source_name`            | `Contact.hs_analytics_source_data` | direct                  |                                                                                                                                                                              |
| `Lead.referrer_name`          | `Contact.referrer_name__c`         | custom\_field\_required | HubSpot custom property created to store LeadSimple's Referrer Name for segmentation.                                                                                        |
| `Lead.tag_list`               | `Contact.tags__c`                  | custom\_field\_required | LeadSimple tags stored as a HubSpot custom text property; comma-separated values for list-building.                                                                          |
| `Lead.annual_contract_value`  | `Deal.amount`                      | direct                  |                                                                                                                                                                              |
| `Lead.cost`                   | `Deal.cost__c`                     | custom\_field\_required | LeadSimple cost stored as a HubSpot custom number property on the associated deal.                                                                                           |
| `Lead.created_at`             | `Contact.original_create_date__c`  | custom\_field\_required | HubSpot CreatedDate is set at migration time; original LeadSimple create date preserved as custom datetime.                                                                  |
| `Lead.closed_at`              | `Deal.closedate`                   | direct                  |                                                                                                                                                                              |
| `Lead.next_task_due_at`       | `Deal.hs_next_task_date`           | direct                  |                                                                                                                                                                              |
| `Lead.assigned_to`            | `Contact.hubspot_owner_id`         | transformed             | Owner resolved by email match to HubSpot users. Unmatched owners flagged for admin action.                                                                                   |
| `Lead.pipeline_name`          | `Deal.pipeline`                    | direct                  |                                                                                                                                                                              |
| `Lead.stage_name`             | `Deal.dealstage`                   | value\_mapping          | LeadSimple stage names map to HubSpot deal stage values per pipeline. Stage probability reapplied from HubSpot side.                                                         |
| `Lead.stage_status`           | `Deal.dealstage`                   | value\_mapping          | Active/Won/Lost/On Hold map to HubSpot deal stage values. 'Closed At' timestamp aligns with deal closedate.                                                                  |
| `Lead.number_of_units`        | `Property.number_of_units__c`      | custom\_field\_required | Units count stored as custom property on the Property custom object in HubSpot.                                                                                              |
| `Lead.property_type`          | `Property.property_type__c`        | custom\_field\_required | LeadSimple property type (Single Family, Multi-Family, etc.) becomes a picklist property on the Property custom object.                                                      |
| `Lead.occupancy`              | `Property.occupancy_status__c`     | custom\_field\_required | LeadSimple occupancy status maps to a custom picklist on the Property custom object (Occupied, Vacant, Under Renovation).                                                    |
| `Property.property_address`   | `Property.address`                 | direct                  |                                                                                                                                                                              |
| `Property.property_name`      | `Property.name`                    | direct                  |                                                                                                                                                                              |
| `Unit.unit_name`              | `Unit.name`                        | direct                  |                                                                                                                                                                              |
| `Unit.monthly_rent`           | `Unit.monthly_rent__c`             | custom\_field\_required | Unit rent amount stored as custom currency property on the Unit custom object.                                                                                               |
| `Unit.lease_end_date`         | `Unit.lease_end_date__c`           | custom\_field\_required | Lease end date stored as custom date property on the Unit custom object.                                                                                                     |
| `Process.process_name`        | `Process.name`                     | direct                  |                                                                                                                                                                              |

## What to watch for in a LeadSimple to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### LeadSimple's property-centric data model has no direct HubSpot equivalent

LeadSimple's core objects — properties, units, and processes — are property-management primitives that don't map to any native HubSpot CRM object.

How we handle it

HubSpot has no concept of a property with occupancy status, unit-level rent tracking, or lease-end date management. FlitStack AI creates HubSpot custom objects for Property and Unit, but these require ongoing admin configuration. Teams should plan which property attributes need reporting dashboards, because HubSpot's standard deal and contact reports won't surface unit-level data without custom report types built on the custom objects.

high

### LeadSimple's Autopilot automation cannot migrate to HubSpot workflows

LeadSimple Autopilot runs property-specific triggers — lease renewal reminders, delinquency alerts, and make-ready task scheduling — that are deeply tied to LeadSimple's property and process objects.

How we handle it

HubSpot workflows operate on CRM objects (contacts, companies, deals, tickets) and marketing events (form submissions, email opens). The automation logic has no structural equivalent in HubSpot. FlitStack AI exports LeadSimple Autopilot rules as a plain-language reference document so your HubSpot admin can rebuild them using HubSpot's workflow builder and the Process custom object created during migration.

medium

### LeadSimple's email stability issues may have created data quality gaps

G2 reviewers consistently report that LeadSimple's email system throws errors after sending or closing messages, requiring page reloads.

How we handle it

When email logging is unreliable, engagement history in LeadSimple may be incomplete — calls and texts may be logged while email activity is missing. FlitStack AI validates engagement counts during the sample migration phase and flags contacts with unusually low email activity for manual review. Teams should audit their LeadSimple email log completeness before migration to understand which contacts may have missing engagement history.

medium

### LeadSimple's tag-to-HubSpot tag translation requires list-rebuilding

LeadSimple's tag list on leads is a flat string field with comma-separated values.

How we handle it

HubSpot's tag concept is a native contact property that supports multiple values but works differently for segmentation and list-building. HubSpot lists use static or dynamic criteria based on contact properties — they don't consume LeadSimple's tag field natively. FlitStack migrates tags as a custom contact property (tags\_\_c) so the data is preserved, but HubSpot lists that replicate LeadSimple's tag-based segmentation need to be rebuilt using HubSpot's list builder with the custom property as the criteria field.

low

### LeadSimple's per-door pricing model means property counts affect migration scope

LeadSimple bills Operations at $1.35 per door per month, and property-count growth is a common trigger for upgrade conversations.

How we handle it

HubSpot has no door-count concept — contacts, companies, and deals are the billing units. Teams migrating from LeadSimple often underestimate how many active properties and units they have because LeadSimple's per-door pricing doesn't surface property counts in the same way. FlitStack AI audits property and unit record counts as part of the discovery phase so migration scope is accurately scoped before pricing is finalized.

## How the migration runs

1. ### Audit LeadSimple data export and assess property/unit record counts

   FlitStack AI pulls a full export from LeadSimple using the platform's CSV export for leads, plus API access for properties, units, and process records.

   What this step covers

   We count all records by type, identify custom field definitions on contacts, properties, units, and processes, and flag any records with missing required fields. This audit produces the record-count breakdown that drives migration scope and pricing. Teams with large property portfolios should also identify which properties are active (occupied, under management) versus archived — archived records can be archived in HubSpot rather than imported as active custom object records.

2. ### Create HubSpot custom objects for Property, Unit, and Process

   Before any data moves, FlitStack AI creates the HubSpot custom objects that have no native equivalent — Property, Unit, and Process — with all required custom properties mapped from the LeadSimple schema.

   What this step covers

   Property and Unit custom objects are associated via a custom relationship property. Process custom object is created with stage, due date, and assigned owner properties. HubSpot admin credentials are used to create these objects in the target portal. We deliver a setup checklist so your admin can verify the custom object schema before validation begins.

3. ### Resolve owners by email match and validate contact-company associations

   LeadSimple owner IDs are matched to HubSpot users by email address.

   What this step covers

   Unmatched owners are flagged in a pre-migration report — your team either creates HubSpot user accounts for them or assigns their records to a designated fallback owner before migration runs. LeadSimple leads without a primary property association map to HubSpot contacts without a company link; contacts with multiple property associations are linked to a primary property record and the additional associations are noted in a custom property for reconciliation.

4. ### Run sample migration with field-level diff across 100–500 records

   A representative sample migrates first — covering contacts from different pipeline stages, properties with varying occupancy, units with different lease terms, and a few process records.

   What this step covers

   FlitStack AI generates a field-level diff showing source value versus destination value for every mapped field. You verify that LeadSimple tags appear correctly in HubSpot's tags\_\_c custom property, that property associations link to the correct Unit and Property custom objects, and that owner resolution produced the expected HubSpot owner on each record. No full run commits until you sign off on the sample.

5. ### Execute full migration with delta-pickup window and audit log

   Full migration runs against HubSpot's API, processing contacts, properties, units, process records, and engagement history.

   What this step covers

   A 24–48 hour delta-pickup window captures any records created or modified in LeadSimple during the cutover period. Every operation is logged in an audit report — record count by object, field mapping applied, owner resolution outcome, and any records that failed with error codes. One-click rollback reverts all migrated records if reconciliation reveals unexpected data loss. After rollback window closes, the audit log is delivered as a migration certificate.

![](https://flitstack.ai/platforms/leadsimple.png) LeadSimple ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 25,000 records** Typical, smaller accounts

**5–7 days for over 250,000 records or heavy custom-object / process configurations** Large or heavily customised accounts

A quote scales with the number of LeadSimple records — contacts, leads, properties, units, and processes all count toward the total. Custom field count drives complexity because each LeadSimple custom field on contacts, properties, or processes requires a corresponding HubSpot custom property and type-aware mapping. Property-to-custom-object translation adds scope when LeadSimple's property associations need to become HubSpot custom objects with junction records. HubSpot CRM-only migrations with minimal custom fields fall in the lower range; full property-management data model migrations with multiple custom objects land in the upper range. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for LeadSimple to HubSpot →](https://flitstack.ai/contact)

## Why teams move from LeadSimple to HubSpot

- LeadSimple users report persistent email bugs — errors after sending or closing emails disrupt communication workflows and require page reloads to recover. HubSpot's email infrastructure is more stable with built-in tracking, sequencing, and deliverability monitoring that integrates natively with the CRM contact record.
- LeadSimple's integration ecosystem is narrow — limited to AppFolio and Buildium for property management sync. HubSpot offers 1,000+ integrations through its App Marketplace and a robust API. Teams moving to HubSpot gain connectivity to their full tech stack without workarounds.
- Property managers using LeadSimple for both CRM and operations hit platform limits when marketing automation and advanced reporting become necessary. HubSpot's Marketing Hub, Service Hub, and analytics platform are built on the same contact database — eliminating the silo between sales, marketing, and service data.
- LeadSimple's workflow automation is property-specific (lease renewals, make-ready triggers) and doesn't connect to marketing campaigns or service tickets. HubSpot's workflow engine operates across all CRM objects and integrates with HubSpot's email marketing, form submissions, and ticket management from a single platform.

Questions, answered

## LeadSimple to HubSpot migration questions

How long does a LeadSimple to HubSpot migration take?

Most LeadSimple-to-HubSpot migrations complete in 48–72 hours of clock time for under 25,000 records across leads, contacts, properties, units, and processes. Larger setups with 250,000+ records or multiple custom objects (Property, Unit, Process) extend to 5–7 days. The longest planning step is creating HubSpot custom objects and validating the property-to-custom-object association model before data lands. Custom field count and the number of active properties in LeadSimple are the primary timeline drivers.

Will my LeadSimple Autopilot workflows migrate to HubSpot?

No. FlitStack AI migrates data and schema only — LeadSimple Autopilot automations (lease renewal reminders, make-ready triggers, delinquency alerts) do not transfer to HubSpot because HubSpot's workflow engine operates on CRM objects and marketing events, not property-management process logic. We export your LeadSimple Autopilot rules as a plain-language reference document so your HubSpot admin can rebuild them using HubSpot's workflow builder and the Process custom object. This is the most manual part of any LeadSimple-to-HubSpot migration and should be scoped as a separate implementation task.

What happens to LeadSimple properties and units in HubSpot?

LeadSimple properties and units have no native equivalent in HubSpot — they become HubSpot custom objects named 'Property' and 'Unit'. Property address, type, occupancy status, and unit count become custom properties on the Property custom object. Units are child records linked to their parent Property via a custom association property. Unit-level rent and lease-end dates become custom properties on the Unit custom object. HubSpot's native deal pipeline is used for sales-activity tracking; property-management reporting requires custom report types built on the custom objects after migration.

Can I migrate LeadSimple custom fields to HubSpot?

Yes. LeadSimple custom fields on contacts, properties, units, and processes map to HubSpot custom properties with type-aware translation — text fields become text properties, picklists become picklists with value-by-value mapping, date fields become date properties. Multi-select picklists in LeadSimple become HubSpot multi-checkbox properties. Each LeadSimple custom field definition is reviewed during discovery, and HubSpot custom properties are pre-created before the migration runs. Custom field count is a pricing driver because each one requires type-aware mapping and validation.

What happens to LeadSimple tags in HubSpot?

LeadSimple tag lists are stored as a custom contact property (tags\_\_c) in HubSpot with comma-separated values. HubSpot's native tag concept is used differently for contact management, so tags don't appear as HubSpot native tags. To replicate LeadSimple's tag-based segmentation in HubSpot, you rebuild lists using HubSpot's list builder with tags\_\_c as the criteria property. This is a post-migration task your admin can complete using the exported tag values as a reference. Tags on properties and units are stored as custom properties on their respective custom objects.

Does the migration affect my LeadSimple account during cutover?

No. FlitStack AI uses scoped read access on LeadSimple via the export API and CSV extraction — your team keeps working in LeadSimple throughout the migration. A delta-pickup window (24–48 hours) captures any leads, properties, or process records created or modified during the cutover so HubSpot reflects LeadSimple's final state at go-live. No write operations occur in LeadSimple. Your LeadSimple account remains fully functional and billed at its current plan until you decide to reduce seats or cancel after go-live.

What data does not migrate from LeadSimple to HubSpot?

The following LeadSimple data does not migrate: Autopilot workflow definitions and process automation logic (must be rebuilt in HubSpot), property management integrations with AppFolio and Buildium (must be reconnected in HubSpot via their respective integrations), and LeadSimple's per-door billing model (HubSpot has no door-count concept — your HubSpot subscription is based on user seats and marketing contacts). Engagement history that was lost due to LeadSimple's email bugs, as documented in the sample migration's data quality audit, is noted but cannot be recovered from LeadSimple's API if it was never logged.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Odoo CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/odoo-crm/to/hubspot) [**Aweber to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/aweber/to/hubspot) [**Clio to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/clio/to/hubspot) [**Customer.io to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/customer-io/to/hubspot) [**Snovio to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/snovio/to/hubspot) [**Dubsado to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dubsado/to/hubspot) [**LeadSimple to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/leadsimple/to/salesforce-sales-cloud) [**LeadSimple to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/leadsimple/to/zoho-crm)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from LeadSimple to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
