CRM migration
Field-level mapping, validation, and rollback between Acquaint CRM and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.
Acquaint CRM
Source
HubSpot
Destination
Compatibility
12 of 12
objects map 1:1 between Acquaint CRM and HubSpot.
Complexity
BStandard
Timeline
3–5 days
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a 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
HubSpot
Contact
1:1Direct 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
HubSpot
Company
1:1Direct 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
HubSpot
Custom Object (property)
1:1Acquaint 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)
HubSpot
HubSpot Files + Custom Object associations
1:1Property 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
HubSpot
Deal
1:1Direct 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
HubSpot
Pipeline
1:1Acquaint 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
HubSpot
Deal Stage
1:1Acquaint 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
HubSpot
Engagement / Note
1:1Acquaint 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)
HubSpot
HubSpot Files
1:1Acquaint 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
HubSpot
HubSpot Owner
1:1Acquaint 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)
HubSpot
No equivalent in HubSpot
1:1Acquaint'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
HubSpot
HubSpot custom properties or custom object fields
1:1Acquaint 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.
| Acquaint CRM | HubSpot | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Property | Custom Object (property)1:1 | Fully supported | |
| Property (photos, floor plans, virtual tours) | HubSpot Files + Custom Object associations1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Pipeline Stage | Deal Stage1:1 | Fully supported | |
| Note | Engagement / Note1:1 | Fully supported | |
| Attachment (document, certificate, contract) | HubSpot Files1:1 | Fully supported | |
| Owner / User | HubSpot Owner1:1 | Fully supported | |
| Client Accounting (ledger entries, invoices) | No equivalent in HubSpot1:1 | Fully supported | |
| Acquaint custom fields | HubSpot custom properties or custom object fields1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Acquaint CRM gotchas
Property data is split across three distinct modules
eSign and SMS data is exportable only as history, not as active configurations
Accounts and client money are tracked within the CRM rather than in a separate accounting package
Custom fields are per-agency and require manual inventory before migration
HubSpot gotchas
Marketing Contacts billing model is migration-critical
Feature tier gating is not visible until onboarding
Mandatory onboarding fees inflate year-one cost
HubSpot CSV importer cannot migrate engagements or attachments
Custom objects require Enterprise and a pre-existing schema
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
Acquaint CRM
Source
Strengths
Weaknesses
HubSpot
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Acquaint CRM and HubSpot.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Acquaint CRM: Rate limit details are not publicly documented on the pricing or help pages.
Data volume sensitivity
Acquaint CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Acquaint CRM to HubSpot migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Acquaint CRM
Other ways to arrive at HubSpot
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.