---
title: "Wise Agent to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Wise Agent 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/wise-agent/to/hubspot"
---

# Wise Agent to HubSpot migration

Moving from Wise Agent to HubSpot brings real estate agents into a platform with broader pipeline management, integrated marketing automation, and a larger ecosystem of integrations. FlitStack AI maps every contact, transaction, label, and activity — preserving original timestamps and owner assignments — while surfacing drip campaigns and automations that must be rebuilt in HubSpot's workflow engine.

Short answer

FlitStack AI migrates contacts, companies, deals, deal stages and custom multi-select properties from Wise Agent 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: 24–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/wise-agent/to/hubspot#field-mapping)

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

Source Wise Agent ![](https://flitstack.ai/platforms-trim/wise-agent.webp)

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

Contact Company Deal Deal Stage Custom Multi-Select Property

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

## What moves from Wise Agent to HubSpot?

Wise Agent and HubSpot serve different CRM philosophies.

Read the full summary

Wise Agent bundles contact management, drip campaigns, transaction tracking, and text marketing into a flat-rate package built for solo real estate agents and small teams. HubSpot separates CRM objects (Contacts, Companies, Deals, Tickets), marketing-automation logic, and reporting into distinct modules with its own property model, lifecycle-stage framework, and per-seat or marketing-contact billing. We migrate all standard objects: contacts to HubSpot contacts, companies to HubSpot companies, transactions to HubSpot deals with original property-address data preserved, and activity history (tasks, notes, emails, calls) with original timestamps and owner links. Wise Agent labels and tags migrate as a custom multi-select property on each contact and company record. What does not migrate: drip campaigns, email templates, text-message sequences, automated follow-up rules, and MLS integration configurations. These are platform-native automation constructs with no HubSpot equivalent that preserves the original logic. We export your Wise Agent drip campaign definitions as a rebuild reference so your HubSpot admin can reconstruct them in HubSpot's workflow builder. The migration runs against the Wise Agent REST API (OAuth 2.0) and the HubSpot API v3. We use scoped read access on Wise Agent during cutover, capture a delta window for in-flight changes, and commit everything to HubSpot with a field-level diff report before final sign-off.

direct

### Contact → Contact

Wise Agent contacts map directly to HubSpot contacts.

How it maps

The contact's primary email, phone, address, and name fields transfer as HubSpot native properties. Owner resolution happens by email match against HubSpot user accounts — unmatched owners are flagged before migration commits.

direct

### Company → Company

Wise Agent company records (typically brokerage or franchise names) map to HubSpot companies.

How it maps

Company domain, name, phone, and address fields migrate as HubSpot company properties. Multiple contacts per company collapse to the HubSpot association model where one contact is primary and others link via company associations.

transformed

### Transaction → Deal

Wise Agent transactions are the core real-estate object and map to HubSpot deals.

How it maps

Property address fields (street, city, state, zip) are created as custom deal properties since HubSpot deals do not have native address fields. Transaction checklists, status, and agent assignments migrate as deal custom properties and deal-pipeline stage values.

value\_mapping

### Transaction Stage / Status → Deal Stage

Wise Agent transaction statuses (Active, Under Contract, Closed, Cancelled) map to HubSpot deal stages.

How it maps

We apply a default stage-probability mapping (Active at 20%, Under Contract at 60%, Closed at 100%, Cancelled at 0%) aligned with HubSpot's probability settings. Your team customizes stage names and probability percentages in HubSpot before the full migration runs to match your specific pipeline workflow.

custom\_field\_required

### Label / Tag → Custom Multi-Select Property

Wise Agent labels (Buyer, Seller, Hot Lead, etc.) attach N-to-N across contacts.

How it maps

We consolidate all labels into a custom HubSpot multi-select property (e.g., wa\_labels) on the contact record. This preserves the full label history without requiring a separate tag object.

direct

### Task / Reminder → Task

Wise Agent task reminders and to-do items map directly to HubSpot tasks.

How it maps

Original due dates, task owners (resolved by email match), priority levels, and completion status transfer. Open tasks migrate as open HubSpot tasks with their due dates; completed tasks migrate with their completion timestamp preserved for historical record completeness.

******What moves 13 objects

Wise Agent HubSpot

- Contact Contact 1:1
- Company Company 1:1
- Transaction Deal transformed
- Transaction Stage Deal Stage transformed
- Label Custom Multi-Select Property transformed
- Task Task 1:1

\+ 7 more in the mapping below

## How Wise Agent 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             | Wise Agent                                                                                                     | HubSpot                                                                                                       |
| --------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Pricing model         | Wise Agent charges a flat $49/month rate regardless of contact count or team size                              | HubSpot tiers pricing per seat (Starter, Pro, Enterprise) with add-ons for marketing contacts and automation  |
| Contact properties    | Wise Agent uses a flat property model with custom fields per contact and label/tag assignment                  | HubSpot uses lifecycle\_stage, custom properties, and association properties on the contact record            |
| Deal/pipeline model   | Wise Agent transactions include property-address fields, transaction checklists, and agent-assignment natively | HubSpot deals store amount, stage, close date, and custom properties; property address requires custom fields |
| Automation paradigm   | Wise Agent drip campaigns and follow-up sequences are platform-native with visual builders                     | HubSpot workflows use triggers, IF/THEN branches, and enrollment criteria — entirely separate product         |
| MLS integration       | Wise Agent has built-in MLS listing sync and IDX connectivity for real estate agents                           | HubSpot has no native MLS integration; requires third-party connector or custom API build                     |
| Billing contact model | Wise Agent has no marketing-contact billing distinction; all contacts count the same                           | HubSpot bills per marketing contact (contacts eligible for marketing emails); non-marketing contacts are free |
| Text/SMS marketing    | Wise Agent includes text-message marketing in its flat rate bundle                                             | HubSpot SMS is a separate paid add-on ($15/month) and requires its own compliance setup                       |

## Wise Agent to HubSpot field mapping

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

******Field mapping 5 shown

Wise Agent HubSpot

1. `firstname` Contact `firstname` Contact
2. `lastname` Contact `lastname` Contact
3. `email` Contact `email` Contact
4. `phone` Contact `phone` Contact
5. `mobilephone` Contact `mobilePhone` Contact

| Wise Agent field               | HubSpot field                         | Mapping                 | Note                                                                                                                                |
| ------------------------------ | ------------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| `Contact.firstname`            | `Contact.firstname`                   | direct                  |                                                                                                                                     |
| `Contact.lastname`             | `Contact.lastname`                    | direct                  |                                                                                                                                     |
| `Contact.email`                | `Contact.email`                       | direct                  |                                                                                                                                     |
| `Contact.phone`                | `Contact.phone`                       | direct                  |                                                                                                                                     |
| `Contact.mobilephone`          | `Contact.mobilePhone`                 | direct                  |                                                                                                                                     |
| `Contact.address`              | `Contact.address`                     | direct                  |                                                                                                                                     |
| `Contact.city`                 | `Contact.city`                        | direct                  |                                                                                                                                     |
| `Contact.state`                | `Contact.state`                       | direct                  |                                                                                                                                     |
| `Contact.zip`                  | `Contact.zip`                         | direct                  |                                                                                                                                     |
| `Contact.source`               | `Contact.hs_analytics_source`         | direct                  | Wise Agent lead source maps to HubSpot's analytics source data property.                                                            |
| `Contact.label`                | `Contact.wa_labels`                   | custom\_field\_required | Wise Agent labels consolidated into a custom multi-select property since HubSpot has no native tag equivalence for contact records. |
| `Contact.createddate`          | `Contact.original_create_date`        | custom\_field\_required | HubSpot CreatedDate is set at migration time; original Wise Agent create date preserved as custom datetime field.                   |
| `Contact.updateddate`          | `Contact.original_last_modified_date` | custom\_field\_required | Original last-modified timestamp preserved as custom field for audit continuity.                                                    |
| `Contact.agent_id`             | `Contact.ownerId`                     | transformed             | Wise Agent agent ID resolved by email match against HubSpot users. Unresolved owners flagged before migration.                      |
| `Company.name`                 | `Company.name`                        | direct                  |                                                                                                                                     |
| `Company.domain`               | `Company.domain`                      | direct                  |                                                                                                                                     |
| `Company.phone`                | `Company.phone`                       | direct                  |                                                                                                                                     |
| `Company.address`              | `Company.address`                     | direct                  |                                                                                                                                     |
| `Company.createddate`          | `Company.original_create_date`        | custom\_field\_required | Original create date preserved as custom datetime for reporting continuity.                                                         |
| `Transaction.transaction_id`   | `Deal.dealname`                       | transformed             | Transaction ID appended to deal name for traceability; original transaction reference stored in custom property.                    |
| `Transaction.amount`           | `Deal.amount`                         | direct                  |                                                                                                                                     |
| `Transaction.stage`            | `Deal.dealstage`                      | value\_mapping          | Wise Agent transaction stages mapped to HubSpot deal stages; stage probability re-applied per HubSpot pipeline configuration.       |
| `Transaction.closedate`        | `Deal.closedate`                      | direct                  |                                                                                                                                     |
| `Transaction.property_address` | `Deal.wa_property_address`            | custom\_field\_required | HubSpot deals have no native address field; property address stored as custom text property on deal.                                |
| `Transaction.property_city`    | `Deal.wa_property_city`               | custom\_field\_required | Custom text property for property city, created on HubSpot deal object before migration.                                            |
| `Transaction.property_state`   | `Deal.wa_property_state`              | custom\_field\_required | Custom text property for property state.                                                                                            |
| `Transaction.property_zip`     | `Deal.wa_property_zip`                | custom\_field\_required | Custom text property for property zip code.                                                                                         |
| `Transaction.checklist_status` | `Deal.wa_transaction_checklist`       | custom\_field\_required | Transaction checklist status migrates as a custom text or multi-select property depending on structure.                             |
| `Transaction.agent_id`         | `Deal.ownerId`                        | transformed             | Transaction agent resolved by email match against HubSpot user accounts.                                                            |
| `Transaction.createddate`      | `Deal.original_create_date`           | custom\_field\_required | Original transaction create date preserved as custom datetime on deal.                                                              |

## What to watch for in a Wise Agent 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

### Drip campaigns and automated sequences do not migrate — they must be rebuilt in HubSpot workflows

Wise Agent's drip campaigns (automated email and text sequences triggered by contact actions, dates, or stage changes) are platform-native automation constructs.

How we handle it

HubSpot's workflow engine uses a different trigger-action model with enrollment criteria, IF/THEN branches, and delay settings that do not accept Wise Agent's campaign logic as importable data. We export your Wise Agent drip campaign definitions (enrollment rules, message content, send timing) as a structured reference document so your HubSpot admin can rebuild them. This is manual work your team must plan for — it is the largest non-data migration task in a Wise Agent to HubSpot move.

high

### HubSpot's marketing-contact billing model creates a cost decision Wise Agent does not require

Wise Agent bills a flat monthly rate regardless of how many contacts exist in your account.

How we handle it

HubSpot separates contacts into marketing contacts (eligible for marketing emails, billed per tier) and non-marketing contacts (free but not emailable). During migration, every contact that was in a Wise Agent drip campaign or had marketing opt-in status gets flagged as a potential marketing contact in HubSpot. Your team decides which contacts are designated marketing contacts based on your email compliance strategy — this affects HubSpot billing and must be configured before the migration commits.

medium

### Wise Agent labels require custom property creation in HubSpot before migration

Wise Agent's flexible labeling system lets you tag contacts with multiple labels (Buyer, Seller, Hot Lead, Referral, etc.) across your entire database.

How we handle it

HubSpot does not have a native N-to-N label/tag object for contacts. We resolve this by creating a custom multi-select property (wa\_labels) on the HubSpot contact object and mapping each unique Wise Agent label to a pick-list value. If you have more than 50 unique labels, the multi-select approach still works but your HubSpot admin should review the list for consolidation opportunities before migration — overly granular labels create clutter in HubSpot's filtering and list-building tools.

medium

### Wise Agent transactions need custom address properties in HubSpot deals

Wise Agent's transaction records include property street address, city, state, and zip as native fields.

How we handle it

HubSpot deals do not have a native address structure — deal records store amount, stage, close date, and custom properties. We create custom text properties on the HubSpot deal object (wa\_property\_address, wa\_property\_city, wa\_property\_state, wa\_property\_zip) to preserve the property address data. Your team needs to create these properties in HubSpot before migration runs, or we create them during the migration with your pre-approval.

medium

### MLS integration and IDX connectivity cannot be migrated — must be rebuilt separately

Wise Agent includes built-in MLS listing sync and IDX connectivity that pulls property listings directly into the CRM.

How we handle it

HubSpot has no native MLS integration — achieving the same listing-pull functionality requires a third-party connector (such as a Real estate-specific HubSpot integration from a provider like Buildout, RealtyNinja, or a custom API integration) or a manual listing-update process. This integration must be sourced, configured, and tested independently of the CRM data migration.

## How the migration runs

1. ### Audit Wise Agent data and configure HubSpot properties before migration

   We begin every Wise Agent to HubSpot migration with a data audit: export your full Wise Agent contact, company, transaction, label, task, note, and calendar event records via the Wise Agent REST API (OAuth 2.0).

   What this step covers

   We profile the data for completeness (missing emails, duplicate records, unlabeled contacts) and document all custom fields in use. Simultaneously, we create the custom HubSpot properties identified in the field-mapping plan — particularly wa\_labels on contacts and the wa\_property\_\* fields on deals — so the schema is ready before data validation begins.

2. ### Resolve Wise Agent agents to HubSpot users by email match

   Wise Agent stores an agent/user on every contact, company, transaction, task, and calendar event.

   What this step covers

   We resolve each Wise Agent agent by email against your HubSpot user list. Agents without a corresponding HubSpot user account are flagged with their Wise Agent record count so your team can decide whether to create HubSpot accounts for them or reassign their records to a fallback owner. No record migrates without a resolved HubSpot owner — this prevents orphaned records in HubSpot after migration.

3. ### Run a sample migration with field-level diff on a representative data slice

   We migrate a sample slice — typically 200–500 records spanning contacts across label categories, active and closed transactions, and a mix of task and note types — and generate a field-level diff report.

   What this step covers

   This report shows every mapped field, its source value in Wise Agent, and its destination value in HubSpot. You review the diff to verify label mapping, transaction-stage mapping, owner resolution, and address preservation before the full migration runs. Sample migration findings feed back into the field-mapping configuration before the full commit.

4. ### Execute full migration with scoped read access and delta-pickup window

   The full migration runs against the Wise Agent API, processing all contacts, companies, transactions, tasks, notes, and calendar events.

   What this step covers

   We use scoped read access on Wise Agent — your team continues working in Wise Agent throughout migration. A delta-pickup window (24–48 hours after initial migration completes) captures any records created or modified during the cutover period. The delta window is applied before final reconciliation so HubSpot reflects Wise Agent's final state at go-live.

5. ### Deliver reconciliation report and drip campaign export for HubSpot workflow rebuild

   After the delta window closes, we generate a full reconciliation report: record counts by object, records migrated vs. skipped vs. failed, owner resolution summary, and a custom-property creation summary.

   What this step covers

   We also deliver the structured drip campaign export (campaign name, enrollment rules, message content, send timing, and stage-trigger logic) as a rebuild reference for HubSpot workflows. One-click rollback is available within 48 hours of final commit if reconciliation reveals data integrity issues requiring a do-over.

![](https://flitstack.ai/platforms/wise-agent.svg) Wise Agent ![](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

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

**5–10 days for over 100,000 records, complex label mapping, or multi-agent team structures** Large or heavily customised accounts

Wise Agent to HubSpot migrations land in the lower-to-mid range because the object model is relatively aligned — contacts, companies, and deals transfer directly. Costs scale upward when Wise Agent uses extensive custom fields per transaction, stores multiple labels per contact that require a multi-select property rebuild in HubSpot, or when the team has more than 20 agents whose owner records need email-matching resolution against HubSpot user accounts. Transaction checklists and property-address fields require custom HubSpot property creation before data can land. The delta-pickup window and field-level diff validation are included in every migration. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Wise Agent to HubSpot

- Teams outgrow Wise Agent's flat-pipeline model as transaction volume increases — HubSpot's deal pipelines support multiple stages, probability forecasting, and deal-specific custom properties that scale beyond a single transaction view. As transaction counts grow into the hundreds per agent, the inability to visualize deal health across multiple stages in Wise Agent creates blind spots in forecasting and pipeline management that HubSpot's multi-stage deal pipelines directly address.
- HubSpot's integration ecosystem (250+ native connectors vs. Wise Agent's limited MLS and lead-source integrations) enables teams to connect their CRM to broader sales, marketing, and analytics stacks as the business diversifies. This matters when teams need to pull data from accounting software, real estate platforms, or marketing tools into their CRM — capabilities that Wise Agent's limited integration library does not support.
- Agents seeking built-in landing pages, form hosting, and email marketing within the same CRM platform find HubSpot's Marketing Hub provides those capabilities without requiring a separate subscription, which Wise Agent handles but at its flat-rate ceiling for feature depth. HubSpot's Marketing Hub scales with marketing sophistication — from basic email broadcasts to advanced workflow-based nurturing — without requiring a separate tool stack.
- Growing teams with multiple agents need role-based permissions, team-level reporting, and territory management — features available in HubSpot's paid tiers that Wise Agent's small-team model does not expose. These capabilities become essential when managing more than five agents or dividing markets into geographic territories with separate performance metrics and access controls.
- When real estate brokerages consolidate multiple agents or teams onto a single CRM post-acquisition, HubSpot's per-seat licensing and company-association model handles that consolidation more cleanly than Wise Agent's flat account structure. The ability to associate contacts and deals with specific brokerages or franchises as HubSpot company records provides the hierarchical structure that multi-office real estate organizations require.

Questions, answered

## Wise Agent to HubSpot migration questions

How long does a Wise Agent to HubSpot migration take?

Most Wise Agent to HubSpot migrations complete in 24–72 hours for databases under 25,000 records. Larger setups with over 100,000 records, extensive custom field configurations, or multiple Wise Agent agents requiring HubSpot user account creation extend to 5–10 days. The longest single step is configuring HubSpot custom properties (particularly the wa\_labels multi-select property on contacts and the wa\_property\_\* address fields on deals) before migration validation runs — these properties must exist in HubSpot before data can land in them.

Will my Wise Agent drip campaigns migrate to HubSpot workflows?

No. FlitStack AI migrates data and schema only — drip campaigns, automated email sequences, text-message automations, and follow-up rules do not transfer to HubSpot. They must be rebuilt in HubSpot's workflow builder using your Wise Agent drip campaign definitions as a reference guide. We export your campaign logic (enrollment triggers, message content, send timing, and stage-change rules) as a structured document your HubSpot admin can use to recreate the sequences. This is the largest non-data migration task in any Wise Agent to HubSpot move.

What happens to my Wise Agent labels in HubSpot?

Wise Agent labels (Buyer, Seller, Hot Lead, Referral, etc.) consolidate into a custom multi-select property called wa\_labels on the HubSpot contact record. Each unique Wise Agent label becomes a pick-list value. If you have more than 50 unique labels, we recommend reviewing the list for consolidation before migration — overly granular label sets create noise in HubSpot's filtering and list-building tools. Labels on companies migrate to a comparable property on the HubSpot company record.

Can I migrate Wise Agent transactions to HubSpot deals?

Yes. Wise Agent transactions map to HubSpot deals, with the transaction amount, stage, close date, and agent owner transferring directly. The property address fields (street, city, state, zip) require custom HubSpot deal properties since deals do not have native address fields. Transaction checklists and custom transaction fields migrate as additional custom deal properties. Stage values are mapped value-by-value to your HubSpot deal pipeline stages.

What does HubSpot's marketing-contact billing model mean for my migrated contacts?

HubSpot bills per marketing contact — contacts eligible to receive marketing emails. After migration, contacts that were enrolled in Wise Agent drip campaigns or have marketing opt-in status should be designated as HubSpot marketing contacts. Your team decides which contacts qualify based on email compliance rules. Non-marketing contacts are free in HubSpot but cannot receive marketing emails. We flag contacts with drip-campaign enrollment history so your team can make the designation during HubSpot setup.

Does the migration affect my Wise Agent account during the cutover?

No. FlitStack AI uses scoped read access on the Wise Agent API during migration — your team continues working in Wise Agent without interruption. A delta-pickup window of 24–48 hours after the initial migration run captures any contacts, transactions, tasks, or notes created or modified during the cutover period. The delta is applied before final reconciliation so HubSpot reflects Wise Agent's complete final state at go-live.

Will my MLS listing sync and IDX connectivity transfer to HubSpot?

No. Wise Agent's MLS integration and IDX listing connectivity cannot be migrated to HubSpot because HubSpot has no native MLS or IDX integration. You will need to source and configure a third-party HubSpot MLS connector (such as Buildout, a real estate-specific HubSpot integration app, or a custom API build) after the CRM migration completes. This is a separate implementation project from the data migration and should be scoped independently.

## 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) [**Civicrm to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/hubspot) [**Lime CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/lime-crm/to/hubspot) [**Systeme IO to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/systeme-io/to/hubspot) [**ChartMogul to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/chartmogul/to/hubspot) [**Marketing Star to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/marketing-star/to/hubspot) [**Iterable to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/iterable/to/hubspot) [**Wise Agent to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/wise-agent/to/salesforce-sales-cloud)

## 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 Wise Agent 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)
