CRM migration

Migrate from Acquaint CRM to HubSpot

Field-level mapping, validation, and rollback between Acquaint CRM and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.

Acquaint CRM logo

Acquaint CRM

Source

HubSpot

Destination

HubSpot logo

Compatibility

100%

12 of 12

objects map 1:1 between Acquaint CRM and HubSpot.

Complexity

BStandard

Timeline

3–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Acquaint CRM is a UK-focused property-management CRM built for estate agents, lettings firms, and property management companies. Its data model centres on Contact, Company, Property (as a first-class object), and Deal, with modules for lettings, sales, property management, and client accounting. HubSpot's CRM uses the standard B2B object model: Contact, Company, Deal, and Ticket — with no native Property equivalent. Acquaint Property records therefore migrate into HubSpot as a custom object or as associations on the Company record, depending on how your Acquaint setup structures property-to-contact relationships. We extract Acquaint data via the REST API at api.acquaintcrm.co.uk (v17.0 endpoints for contacts, companies, properties, and accounts), supplemented by CSV export for ledger and accounting records that HubSpot cannot store natively. Contact, company, and deal fields map directly in most cases. Acquaint owner records resolve to HubSpot users by email match. Property records with photos, floor plans, and virtual tours re-upload to HubSpot Files under the associated Company or custom property object. Original create dates from Acquaint are preserved as custom datetime fields since HubSpot overwrites Createdate at import time. Workflows, email templates, SMS sequences, and branded document templates do not migrate — these require a separate rebuild in HubSpot's automation tools and are outside FlitStack's data-migration scope. We export your Acquaint workflow definitions as a rebuild reference for your HubSpot admin.

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

Acquaint CRM logo

Acquaint CRM

What's pushing teams away

  • The Windows Desktop interface alongside a browser client signals a legacy dual-shell architecture that newer agents find dated compared to cloud-native platforms.
  • Dozens of third-party integrations are mentioned but no native Zapier/Make connector appears in the documentation, making automated workflows harder to extend without developer work.
  • No free tier or trial is prominently offered on the pricing page, which raises the evaluation barrier for small agencies comparing multiple CRM options on a tight budget.
  • Single flat price means large multi-branch operations cannot selectively licence only the modules they need, potentially paying for unused Property Management or Lettings features.

Choosing

HubSpot logo

HubSpot

What's pulling them in

  • Lowest barrier to entry of any major CRM — the free tier with unlimited contacts lets teams validate fit before committing to a paid plan, according to G2 and Capterra reviewers.
  • Native integration between the CRM and sales engagement tools (sequences, email tracking, dialer) means no separate sync configuration, a theme across G2 Sales Hub reviews.
  • Pipeline visualization, deal tracking, and automated workflows are consistently praised as intuitive and easy to set up without developer involvement.
  • Strong onboarding for new team members — reviewers on Capterra and G2 highlight how quickly new reps become productive without formal training.
  • The HubSpot platform ecosystem (Marketing, Sales, Service, CMS hubs) allows growing companies to consolidate tools without building new integrations.

Object mapping

How Acquaint CRM objects map to HubSpot

Each row shows how a Acquaint CRM object lands in HubSpot, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Acquaint CRM

Contact

maps to

HubSpot

Contact

1:1
Fully supported

Direct map to HubSpot Contact. Acquaint contact fields—first name, last name, email, phone, mobilephone, address, city, county, postcode, country, and job title—translate field‑for‑field to HubSpot properties. The primary company association links to the corresponding HubSpot Company record, and owner resolution occurs by email match against HubSpot user accounts. Original create timestamps are stored in a custom datetime property because HubSpot sets its own Createdate at import time.

Acquaint CRM

Company

maps to

HubSpot

Company

1:1
Fully supported

Direct map to HubSpot Company. Acquaint company records—name, website domain, address, city, county, postcode, country, phone, and industry—translate field‑for‑field to HubSpot Company properties. In multi‑branch setups, parent/branch hierarchies map to HubSpot's Parent Company field when the relationship is one‑to‑one. Original create timestamps are preserved in a custom datetime property, as HubSpot sets its own Createdate at import time.

Acquaint CRM

Property

maps to

HubSpot

Custom Object (property)

1:1
Fully supported

Acquaint Property has no HubSpot native equivalent. We create a HubSpot custom object (Property) with standard Acquaint fields mapped: address, bedrooms, property type, listing status, asking price, and rental amount. Each Property links to the associated Company (agency) and Contacts (vendors/tenants) via HubSpot associations.

Acquaint CRM

Property (photos, floor plans, virtual tours)

maps to

HubSpot

HubSpot Files + Custom Object associations

1:1
Fully supported

Property media files—photos, floor plans, virtual tours, and EPCs—are downloaded from Acquaint and re‑uploaded to HubSpot Files, then linked to the appropriate Property custom object or Company record using HubSpot's association API. Original file names and metadata are retained where possible. If a file exceeds HubSpot's 25 MB per‑file limit, we split it into smaller chunks or store a reference URL to the original asset at your preference.

Acquaint CRM

Deal

maps to

HubSpot

Deal

1:1
Fully supported

Direct map to HubSpot Deal. Acquaint deal name, amount, stage, and close date translate to HubSpot Deal properties. If the Acquaint deal is linked to a Property, the Deal links to the migrated HubSpot Property custom object via a Deal-Property association.

Acquaint CRM

Pipeline

maps to

HubSpot

Pipeline

1:1
Fully supported

Acquaint pipeline definitions map directly to HubSpot pipelines. If your Acquaint instance contains multiple pipelines—such as a Sales Pipeline and a Lettings Pipeline—we create matching HubSpot pipelines and configure each stage with the same order and probability percentages you specify. Stage‑level history timestamps from Acquaint are stored in custom datetime fields to maintain activity continuity. Value mapping ensures each Acquaint stage label corresponds to the correct HubSpot deal stage within its pipeline.

Acquaint CRM

Pipeline Stage

maps to

HubSpot

Deal Stage

1:1
Fully supported

Acquaint pipeline stage names—such as 'Offer Accepted', 'Instructed', and 'Under Offer'—map value‑by‑value to HubSpot deal stage labels. We apply your specified stage order and probability percentages per pipeline, and missing stage labels are flagged for confirmation before migration. Stage‑history timestamps from Acquaint are stored in custom datetime fields to preserve activity timelines. This ensures deal progression data reflects the original pipeline logic after cutover.

Acquaint CRM

Note

maps to

HubSpot

Engagement / Note

1:1
Fully supported

Acquaint notes and tasks migrate as HubSpot engagements (type: note or task). Original timestamps, owners, and parent-record links (Contact, Company, Property, or Deal) are preserved. Rich HTML formatting in Acquaint notes is stripped to plain text on import to HubSpot.

Acquaint CRM

Attachment (document, certificate, contract)

maps to

HubSpot

HubSpot Files

1:1
Fully supported

Acquaint attachments on Contact, Company, or Deal records—such as tenancy agreements, EPCs, and contracts—are downloaded and re‑uploaded to HubSpot Files under the matching record. We locate the target record using the Acquaint record ID stored in the Source_ID__c custom property, ensuring accurate linkage. Original file names and creation dates are retained where possible, and any file larger than HubSpot's 25 MB limit is handled as described for property media.

Acquaint CRM

Owner / User

maps to

HubSpot

HubSpot Owner

1:1
Fully supported

Acquaint owner records resolve to HubSpot users by email address. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them first or assigns their records to a fallback owner. No record lands in HubSpot without a resolved OwnerId.

Acquaint CRM

Client Accounting (ledger entries, invoices)

maps to

HubSpot

No equivalent in HubSpot

1:1
Fully supported

Acquaint's client accounting module — bank imports, credit entries, billing ledger — has no HubSpot CRM equivalent. We export these records as CSV for your accounting team to reconcile in your finance system post-migration. This data is not imported into HubSpot.

Acquaint CRM

Acquaint custom fields

maps to

HubSpot

HubSpot custom properties or custom object fields

1:1
Fully supported

Acquaint custom fields on any object map to HubSpot custom properties. Field type mapping: text → string, number → number, date → datetime, pick-list → pick-list, checkbox → boolean. Hidden or deprecated Acquaint fields are flagged for your review before migration.

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.

Acquaint CRM logo

Acquaint CRM gotchas

Medium

Property data is split across three distinct modules

Medium

eSign and SMS data is exportable only as history, not as active configurations

High

Accounts and client money are tracked within the CRM rather than in a separate accounting package

Low

Custom fields are per-agency and require manual inventory before migration

HubSpot logo

HubSpot gotchas

High

Marketing Contacts billing model is migration-critical

High

Feature tier gating is not visible until onboarding

Medium

Mandatory onboarding fees inflate year-one cost

Medium

HubSpot CSV importer cannot migrate engagements or attachments

Medium

Custom objects require Enterprise and a pre-existing schema

Pair-specific challenges

  • Acquaint Property has no native HubSpot equivalent — custom object required

    Acquaint's Property object (with fields for bedrooms, asking price, rental amount, property type, listing status, and photos) has no counterpart in HubSpot's standard CRM schema. We create a HubSpot custom object named Property and map each Acquaint field accordingly. If your Acquaint setup uses property-to-contact N:N relationships (e.g. multiple vendors or tenants per property), those associations require HubSpot's custom-relationship definition on the custom Property object. We validate the association structure with a sample migration before the full run.

  • HubSpot overwrites Createdate on import — original listing dates must be preserved manually

    HubSpot's import wizard and API both set Createdate to the import timestamp. For Contact, Company, Property custom object, and Deal records, original Acquaint create dates are preserved in a custom datetime property (e.g. Original_Create_Date__c). This matters for property listings where the original instruction date drives analytics and reporting continuity. We flag this explicitly in the field mapping plan before migration starts, so your team can confirm the custom field names.

  • Acquaint client accounting records have no destination in HubSpot

    Acquaint's client accounting module stores ledger entries, credit notes, bank import records, and branded document outputs. HubSpot CRM has no accounting or financial ledger capability — these records cannot import into HubSpot. We export the accounting module data as CSV for your finance team to reconcile in your accounting system (Xero, QuickBooks, or similar) post-migration. This is disclosed upfront in the scoping call so no one expects accounting history to appear in HubSpot.

  • Acquaint API rate limits restrict bulk export speed

    Acquaint's REST API at api.acquaintcrm.co.uk enforces a rate limit (approximately 100 requests per 10 seconds per token). For migrations with large property datasets—1,000+ properties each with multiple photos, floor plans, and attachments—the export phase can quickly exhaust that quota. We implement automatic throttling and exponential back‑off in the migration pipeline, using batch export endpoints where available and staggering requests across off‑peak hours to stay within limits. Continuous monitoring logs each API call, and any 429 response triggers a retry after the prescribed wait period, ensuring a reliable and timely export without exceeding Acquaint's constraints.

  • Workflows, SMS sequences, and document templates do not migrate

    Acquaint workflows (property alerts, task reminders, pipeline automation), SMS sequences, and branded document templates are automation logic stored in Acquaint's workflow engine. HubSpot has its own Workflows and Sequences tools that require a separate rebuild. We export Acquaint workflow definitions as JSON and provide a mapping document so your HubSpot admin can reconstruct the logic in HubSpot's automation tools. This is standard scope for all FlitStack CRM migrations and is disclosed before migration starts.

Migration approach

Six steps for a successful Acquaint CRM to HubSpot data migration

  1. Extract Acquaint data via API and CSV

    We connect to Acquaint's REST API (v17.0 endpoints at api.acquaintcrm.co.uk) for contacts, companies, properties, and deals, using paginated requests to retrieve all records in bulk. For the client accounting module we export ledger entries and bank‑import records as CSV because HubSpot cannot store them. We also pull property media files via the file download endpoints. A pre‑migration data audit checks for duplicate records, missing required fields (such as missing email on contacts), and orphaned property‑to‑contact links, producing a data‑quality report that your team reviews before mapping starts.

  2. Design HubSpot custom property object schema

    Acquaint Property objects have no native HubSpot equivalent, so we first create a Property custom object in your HubSpot portal. We define fields that mirror Acquaint’s schema—address, property_type, listing_status, asking_price, bedrooms, bathrooms, rental_amount, and photo_count—and apply type‑aware mapping (e.g., pick‑lists for property_type and listing_status). We also add Original_Create_Date__c custom properties on Contact, Company, Deal, and Property records to preserve the original creation timestamp. All field labels, data types, and pick‑list values are validated in a test portal via the HubSpot API before the production migration begins.

  3. Resolve owners and validate company-contact relationships

    Acquaint owner records resolve to HubSpot users by email match. We run the owner resolution step first and surface any unmatched owners — your team creates HubSpot user accounts for them or designates a fallback owner. Company records must load before contacts so the HubSpot Company association resolves correctly on each contact. Property records load after their associated Company/agency record.

  4. Run a sample migration with field-level diff

    A representative slice of 50–100 records—covering contacts, companies, properties, and deals across various pipeline stages and owner assignments—migrates to your HubSpot portal first. We generate a field‑level diff report that lets you verify property field mapping, company‑contact association integrity, owner resolution by email, and preservation of original create timestamps. The report also highlights any custom property mismatches, missing file attachments, or data‑type issues. After you approve the sample, we proceed to the full migration; the sample validation step typically takes 2–4 hours.

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

    The full migration runs against HubSpot via the CRM API and bulk import wizard. A delta-pickup window (typically 24–48 hours) captures any records created or modified in Acquaint during the cutover period. Each operation is logged in an audit trail. One-click rollback is available if reconciliation identifies missing or mis-mapped records. We deliver a post-migration validation report showing record counts, owner coverage, and any unmapped fields requiring manual resolution.

Platform deep dives

Context on both ends of the pair

Acquaint CRM logo

Acquaint CRM

Source

Strengths

  • Flat per-agency pricing at £99/month with no per-user surcharge for small teams
  • Bundled sales, lettings, and property management in a single licence
  • UK-based telephone and email support included without an additional support tier
  • No minimum contract, no setup fees, and automatic software updates at no extra charge
  • Tightly integrated website hosting and CRM with property portal synchronisation

Weaknesses

  • Dual Windows Desktop + browser interface indicates a legacy desktop-first codebase that may not meet modern UX expectations
  • No native Zapier or Make integration documented, limiting no-code workflow extension
  • Large multi-branch or franchise agencies may pay for unused modules under the single flat-rate model
  • No publicly documented bulk export tool beyond the REST API, which requires technical access to script exports
HubSpot logo

HubSpot

Destination

Strengths

  • Genuinely useful free CRM tier with no seat limit on contact records.
  • All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration.
  • Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews.
  • Workflow automation triggers across contacts, deals, and tickets with a visual builder.
  • API coverage for all standard objects including custom objects at Enterprise tier.

Weaknesses

  • Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×.
  • Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation.
  • Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page.
  • API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing.
  • Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 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 Acquaint CRM and HubSpot.

  • Object compatibility

    B

    1 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

    Acquaint CRM: Rate limit details are not publicly documented on the pricing or help pages.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Acquaint CRM to HubSpot 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 Acquaint CRM to HubSpot data migrations

Answers to the questions buyers ask most during Acquaint CRM to HubSpot migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Acquaint CRM to HubSpot migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Acquaint-to-HubSpot migrations complete within 3–5 days of clock time for datasets under 50,000 records (contacts, companies, properties, and deals combined). Property-heavy datasets with multiple photos and attachments per listing extend the timeline to 7–12 days because each file requires a separate API write to HubSpot Files. The sample migration validation step typically takes 2–4 hours before the full run begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Acquaint CRM.
Land in HubSpot, 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