Migrate from Acquaint CRM to HighLevel

Acquaint contact records map directly to HighLevel contacts. We match by email address and preserve the original createdate as a custom field since HighLevel assigns CreatedDate at import time. Owner resolution runs by email match against HighLevel users before any records land.

Acquaint company records (landlord or vendor businesses) map to HighLevel companies. We preserve the company address, phone, and website fields. If an Acquaint contact has no associated company, the company record is created as a placeholder to maintain referential integrity in HighLevel.

Acquaint property records have no direct HighLevel equivalent. We create a Property Listing custom object in HighLevel and map property address, status, listing price, and property type into custom fields on that object. Each property record links to the associated landlord or vendor contact.

Acquaint tenancy records (tenant contact, start date, end date, rent amount, deposit held) map to a Tenancy custom object in HighLevel linked to the tenant Contact. Rental periods and deposit fields become custom fields on the tenancy record. We also map the deposit amount to a currency field and link the tenancy to the related property custom object using a lookup relationship, ensuring referential integrity across lettings data.

Acquaint tasks map to HighLevel tasks with subject, due date, assigned user, and status preserved. Completed task history migrates as completed HighLevel tasks. Owner resolution by email match ensures tasks are assigned to the correct HighLevel user. Task descriptions, priority flags, and any linked sub‑tasks are also transferred, with the original created timestamps preserved as a custom field to maintain historical context.

Acquaint notes attached to contacts or properties migrate as HighLevel notes. We link each note to the corresponding contact or property custom object. Original created timestamps are preserved in a custom field since HighLevel overwrites CreatedDate on import. Note categories, author email, and any attached files are also transferred, ensuring the full context of each communication is available in HighLevel's activity feed.

Acquaint documents (EPCs, floor plans, tenancy agreements, property photos) are downloaded from the source and re-uploaded as HighLevel files, linked to the relevant contact or property record. Large property-photo sets are batched to stay within HighLevel file-size limits. We preserve original file names and creation dates as metadata, and apply version tags to distinguish updates from the original upload, facilitating audit trails and quick retrieval.

Acquaint contact tags and property tags map to HighLevel tags. Tags are preserved as a flat list on the contact or custom object. No tag hierarchy exists in Acquaint, so a flat tag migration matches the HighLevel model exactly. These tags can be used for segmentation, lead scoring, and workflow triggers in HighLevel, allowing you to replicate existing marketing and routing logic without additional configuration.

Acquaint staff records (name, email, role, branch) map to HighLevel users. Email address is the key field for matching. Unmatched staff are flagged before migration — your team either invites them to HighLevel first or assigns their records to a fallback owner.

Acquaint multi-branch setups can map each branch to a separate HighLevel sub-account, preserving independent contact pools, pipelines, and reporting per branch. Alternatively, all branches consolidate into one HighLevel account with branch-tag filtering — your team chooses before migration planning begins.

Acquaint SMS logs attached to contacts migrate as HighLevel conversation records or tasks with a Type of SMS. HighLevel's Conversations feature captures inbound/outbound SMS threads per contact, preserving the message content and timestamp. Each thread retains direction flags, delivery status, and any media URLs, enabling your team to view full conversation history and trigger automated replies based on inbound keywords.

Acquaint contact custom fields (source of lead, preferred contact method, budget range) are created as HighLevel custom fields on the Contact object before migration. Field data types are matched — pick-lists become pick-lists, text fields become text fields. We also transfer any default values, required flags, and validation rules, ensuring that downstream reporting and automation triggers behave consistently with the original Acquaint setup.