CRM migration
Field-level mapping, validation, and rollback between Acquaint CRM and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Acquaint CRM
Source
Freshsales
Destination
Compatibility
11 of 11
objects map 1:1 between Acquaint CRM and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Acquaint CRM is a property-industry CRM built around sales, lettings, and property management modules — it stores contacts, companies, deals, and property-specific data including listings, valuations, and portal integrations with Rightmove and Zoopla. Freshsales organises data around Leads, Contacts, Accounts, Deals, and Custom Objects, with Contact Lifecycle Stages replacing Acquaint's status model and Freddy AI providing native lead scoring once migrated. We map Acquaint's contact, company, and deal records to Freshsales Contacts, Accounts, and Deals with direct field-name translations for standard fields. Acquaint's property and listing data requires Freshsales Custom Objects or multi-field consolidation — we deliver the schema design before data lands. Workflow rules, property-portal automations, and third-party integrations (Rightmove, Zoopla sync) do not migrate and must be rebuilt in Freshsales using Freshsales Workflows or the REST API. The migration runs against Freshsales' API with bulk operations where supported, rate-limit awareness built in, and a 24–48 hour delta-pickup window capturing any records modified during cutover. Original create dates and owner assignments are preserved via custom fields since Freshsales sets CreatedDate at import time. A sample migration with field-level diff runs first so you can verify mapping logic before the full commit.
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 Freshsales, 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
Freshsales
Contact
1:1Acquaint Contact records migrate directly to Freshsales Contacts. Freshsales requires a primary AccountId on contacts — Acquaint contacts without a linked company are attached to a default 'Unassigned Account' record. Email uniqueness is enforced on the Freshsales side; duplicate emails trigger a merge or skip decision before migration commits.
Acquaint CRM
Company
Freshsales
Account
1:1Acquaint Company maps to Freshsales Account. UK address fields (street, city, postcode) translate to Freshsales' address compound field. Parent-company hierarchies in Acquaint map to Freshsales Account.ParentId. Multi-company associations on contacts collapse to one primary AccountId with additional relationships surfaced as Account Contact Relations.
Acquaint CRM
Deal
Freshsales
Deal
1:1Acquaint Deal maps to Freshsales Deal. Pipeline and stage names are mapped value-by-value since Acquaint pipeline stages are arbitrary strings whereas Freshsales stages are scoped per Sales Pipeline. Deal amount, close date, owner, and custom fields migrate directly with owner resolved by email match to Freshsales users.
Acquaint CRM
Property Listing
Freshsales
Custom Object (Property)
1:1Acquaint's property and listing module has no direct Freshsales equivalent. We create a Freshsales Custom Object named 'Property' with fields for address, listing type (sale/rent), price, status, and links back to the owning Account. Property-to-contact associations are modelled via Freshsales' association API. Portal integration (Rightmove, Zoopla) must be rebuilt in Freshsales using the Freshworks Marketplace apps or custom webhook.
Acquaint CRM
Task / Activity
Freshsales
Task
1:1Acquaint tasks, call logs, and meeting notes map to Freshsales Tasks. Original timestamps, owners, and linked contact/deal references are preserved. Acquaint's SMS Text activities migrate as Freshsales Tasks with Type='SMS'. Call duration and outcome data stored in Acquaint custom fields map to Freshsales custom number and pick-list fields on the Task.
Acquaint CRM
Pipeline Stage
Freshsales
Deal Stage (per Sales Pipeline)
1:1Acquaint pipeline stage names are free-form strings. Each distinct stage name maps to a Freshsales Deal Stage within the target Sales Pipeline. We deliver the full stage-value map as part of the migration plan so your Freshsales admin can create the pipeline stages before data lands. Stage order and probability values are configurable per stage in Freshsales and are applied at migration time.
Acquaint CRM
User / Owner
Freshsales
User
1:1Acquaint user records are resolved against Freshsales users by email address. Unmatched owners are flagged before migration — the team either creates Freshsales user accounts first or assigns those records to a fallback owner. Active/inactive status in Acquaint maps to Freshsales User.Active flag. Owner history on deals is preserved as a custom text field since Freshsales Opportunity stores only the current OwnerId.
Acquaint CRM
Custom Field (Contact)
Freshsales
Custom Field (Contact)
1:1Acquaint custom fields on contacts (e.g., marketing source, property interest type) create as Freshsales Contact custom fields. Field type mapping: Acquaint text → Freshsales text, pick-list → pick-list, date → date, number → number. Custom field IDs from Acquaint are stored in Freshsales' Source_System_ID__c field for traceability. Duplicate field names across objects are de-duplicated during schema design.
Acquaint CRM
Attachment / Document
Freshsales
File
1:1Acquaint document attachments (brochures, floor plans, EPCs linked to properties) are downloaded and re-uploaded to Freshsales Files. File size limits apply (Freshsales default 25MB per file). Inline images in Acquaint notes are extracted and hosted separately, with URLs stored in Freshsales Notes or custom URL fields. Property images associated with listings via the Custom Object require manual re-link after migration.
Acquaint CRM
Valuation
Freshsales
Custom Object (Valuation)
1:1Acquaint valuations attached to properties do not have a Freshsales native equivalent. We create a 'Valuation' Custom Object with fields for property reference, valuation amount, date, agent, and status. The object links back to the Property Custom Object via Freshsales' relationship model. Historical valuations migrate as records on this object.
Acquaint CRM
Lettings Tenancy Record
Freshsales
Custom Object (Tenancy)
1:1Acquaint tenancy and rental management records (tenant details, lease dates, deposit, rent amount) require a 'Tenancy' Custom Object in Freshsales. The object links to the Contact (tenant), the Property, and the Account (landlord). Rent payment history and deposit status are modelled as custom fields — Freshsales does not have a native billing or accounting module.
| Acquaint CRM | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Property Listing | Custom Object (Property)1:1 | Fully supported | |
| Task / Activity | Task1:1 | Fully supported | |
| Pipeline Stage | Deal Stage (per Sales Pipeline)1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Custom Field (Contact) | Custom Field (Contact)1:1 | Fully supported | |
| Attachment / Document | File1:1 | Fully supported | |
| Valuation | Custom Object (Valuation)1:1 | Fully supported | |
| Lettings Tenancy Record | Custom Object (Tenancy)1: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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit Acquaint data model and export structure
We connect to Acquaint CRM via API using your credentials and pull a full export of contacts, companies, deals, tasks, and property records. We count record volumes per object, identify custom fields, flag duplicate emails, and assess property-listing complexity. The output is a data audit report that identifies records requiring special handling — properties with large image galleries, tenancy records with financial history, and contacts with multiple company associations. This step runs read-only and does not touch your Acquaint data.
Design Freshsales schema and agree field mapping
Based on the audit, we design the Freshsales schema: standard objects for contacts, accounts, and deals, plus Custom Objects for Property, Valuation, and Tenancy. We produce a field-mapping spreadsheet with every Acquaint field on the left and its Freshsales destination on the right, including transformation notes for pick-list value mappings and owner-resolution logic. Your Freshsales admin reviews and approves the schema before any data moves. Any Freshsales custom fields not yet created in your account are listed with setup instructions.
Resolve users and set up Freshsales pipeline structure
Acquaint owner IDs are resolved by email against Freshsales users. We provide a pre-migration checklist: create Freshsales user accounts for any Acquaint users who do not yet have a Freshsales login, map each Acquaint pipeline to a Freshsales Sales Pipeline, and create the corresponding stage values. Pipeline and stage setup in Freshsales must be complete before the migration runs because Freshsales Deal.stage is a required pick-list field — records cannot land without a matching stage value already in the system.
Run sample migration with field-level diff
A representative slice migrates first — typically 100–500 records spanning contacts, companies, deals, properties, and a few tasks. We generate a field-level diff comparing source values against destination values for every mapped field. You verify that contact status-to-lifecycle-stage mapping is correct, property records are linked to the right accounts, and deal stages are populated. Any mapping errors are corrected and the sample re-runs until the diff passes. This is the validation gate before the full migration commits.
Execute full migration with delta-pickup window
The full dataset migrates in ordered batches: accounts first, then contacts, then deals, then property custom objects, then tasks. Freshsales API rate limits are managed via adaptive batching. A delta-pickup window of 24–48 hours runs concurrently — any records created or modified in Acquaint during the migration are captured and imported after the main run. Audit logs record every operation. One-click rollback reverts the Freshsales environment to its pre-migration state if reconciliation finds unexpected issues.
Post-migration validation and rebuild handover
We run reconciliation reports comparing record counts and key field values between Acquaint and Freshsales. Missing or incorrectly mapped records are corrected. We deliver a rebuild-reference export for your Freshsales admin: Acquaint workflow definitions, property-portal sync rules, and any Rightmove/Zoopla automation logic — exported as text so your team can reconstruct the equivalent Freshsales Workflows. Integration credentials (email sync, telephony) are reconnected in Freshsales as a post-migration step.
Platform deep dives
Acquaint CRM
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Freshsales.
Object compatibility
2 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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Acquaint CRM to Freshsales 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 Freshsales
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.
