Migrate from Acquaint CRM to Salesforce Sales Cloud

Direct map to Salesforce Contact. Acquaint contact records with a primary company association map to Contact.AccountId using the resolved Account ID from the companies migration sequence. Acquaint contacts without a company link land as standalone Salesforce Contacts without default account assignment unless your team specifies a default account for unassigned contacts during migration setup. All contact fields including name, email, phone, address, and custom fields migrate directly.

Acquaint contacts flagged as early-stage prospects with no associated property deal split into Salesforce Lead records to preserve the unqualified status in the new system. Lead conversion creates the corresponding Contact and Account in Salesforce when the prospect advances to an active engagement, preserving the lead history and original source attribution. This split prevents unqualified prospects from cluttering the sales pipeline while maintaining data continuity.

Acquaint companies map to Salesforce Accounts. UK address formatting is preserved through Salesforce's Address compound field, ensuring postcode and street address components remain separate for reporting and mapping integrations. Parent-child company hierarchies in Acquaint map to Account.ParentId for multi-entity organizations. Multi-company associations on contacts collapse to one primary AccountId plus Account Contact Relations for secondary links.

Sale properties in Acquaint have no direct Salesforce equivalent. We create a Property__c custom object with fields for address, property type (flat, house, commercial), listing price, number of bedrooms, tenure (freehold/leasehold), and EPC rating. Your admin decides whether to link Property__c to the selling Account or use the Account record itself as the property container.

Letting properties in Acquaint require a custom Property__c object with letting-specific fields: monthly rent, deposit amount, available date, letting status (available, under offer, tenanted), and property type. Landlord information links to the landlord's Account or Contact record via a lookup relationship.

Acquaint sales deals map to Salesforce Opportunities using direct field mapping. Deal name becomes Opportunity.Name and deal amount maps to Opportunity.Amount with standard currency formatting preserved. Deal stage maps to Opportunity.StageName with value-by-value mapping against the target Salesforce Sales Process pick-list for that record type, ensuring stage progression logic transfers correctly.

Lettings deals in Acquaint map to Salesforce Opportunities with a letting-specific record type that separates them from sales deals in reporting. Rent amount replaces deal amount as the Opportunity.Amount value. Tenancy start date maps to Opportunity.CloseDate as the expected tenancy commencement. Deal stage reflects viewings, offers, referencing, and move-in milestones specific to the rental lifecycle.

Each Acquaint pipeline (e.g., Sales Pipeline, Lettings Pipeline) becomes a Salesforce Sales Process keyed by a corresponding Record Type on the Opportunity object. Stage names are mapped value-by-value so that 'Offer Received' in Acquaint maps to the equivalent stage name in Salesforce's pick-list for that record type.

Acquaint notes migrate as Salesforce Notes using the ContentNote/ContentDocument model in Lightning Experience for modern UI compatibility. Original timestamps and creating user preserved to maintain audit trail continuity. Rich-text formatting in Acquaint notes is preserved where the format is compatible with Salesforce's note body structure, ensuring notes remain readable in the new system.

Acquaint tasks map directly to Salesforce Tasks with field-level correspondence. Subject becomes Task.Subject, due date maps to Task.ActivityDate, and status and priority fields carry over with value mapping where pick-list values differ between systems. Task ownership transfers based on user email resolution against Salesforce Users. Reminders and recurrence patterns are preserved where applicable.

Acquaint SMS text records migrate as Salesforce Tasks with Task.Type='Text' and the message body stored in Task.Description. Original send timestamp and sender/recipient preserved for conversation history continuity. Note that Salesforce does not send SMS natively — this is an audit record, not a live messaging integration. Two-way SMS would require an AppExchange package post-migration.

Acquaint file attachments (photographs, floor plans, EPCs, virtual tour links) re-upload to Salesforce Files (ContentDocument/ContentVersion model). Files are linked to the parent record (Property__c, Account, or Contact) via ContentDocumentLink. Salesforce's 25MB per-file limit applies; larger files are flagged for manual handling.

Acquaint custom fields on any standard object require creation of equivalent custom fields on the Salesforce side. Field types are mapped type-by-type: text fields become Text(255) or Long Text Area; pick-lists become Salesforce pick-lists; date fields become Date fields. Custom fields without a Salesforce equivalent are stored as reference fields for manual review.

Acquaint multi-branch setups map to Salesforce Territories for geographic assignment or to a hierarchical Account structure where each branch is a child Account under a parent holding company. The approach depends on whether your Salesforce org uses Territories for reporting.

Acquaint user records are matched to Salesforce Users by email address. Records owned by Acquaint users without a corresponding Salesforce user are assigned to a fallback owner (typically a system admin) and flagged in the migration report for manual re-assignment.