Migrate from Acquaint CRM to Twenty CRM

Acquaint Contact records map directly to Twenty's People object. The People record inherits the contact's name, email, phone, job title, and address fields. For Acquaint contacts without a primary company assignment, Twenty's companyId field is left blank and the record lands as an unlinked People entry.

Acquaint Company records map to Twenty's Company object. The company name, website, industry, employee count, and annual revenue fields translate directly. Acquaint's parent-company hierarchy maps to Twenty's linkedinParentId field if configured in the target workspace. Additional address fields such as city, state, and country are also mapped to their corresponding Twenty fields.

Acquaint Property records do not have a direct Twenty equivalent. We translate property records into Twenty Company entries with custom fields appended for property-specific data: property type, tenure, number of bedrooms, EPC rating, and property status. Each property record receives a tag in Twenty marking its origin as an Acquaint property for reporting clarity.

Acquaint Deal records map to Twenty's Opportunity object. The deal name, amount, stage, expected close date, and owner assignment all translate. Acquaint's deal-stage pick-list values are mapped to Twenty's Opportunity Stage select field during migration. Stage-probability values require manual review in Twenty after migration.

Acquaint activity records split by type: calls map to Twenty Tasks with Type='Call', emails map to Tasks with Type='Email', meetings map to Twenty Events, and notes map to the Note object. Original timestamps, subject lines, and body content are preserved. Parent-record links (contactId, companyId, opportunityId) are resolved against migrated IDs.

Acquaint file attachments associated with contacts, companies, or deals are re-uploaded to Twenty as Attachments linked to the corresponding record. File size limits apply (Twenty's upload limit is 25MB per file). Inline images in notes are downloaded and rehosted as Twenty attachments.

Acquaint staff records are resolved against Twenty workspace members by email address matching. We extract all Acquaint owner IDs from records, match each to a Twenty user by email, and assign the Twenty userId as the owner. Unmatched owners are flagged before migration and assigned to a fallback owner in Twenty.

Acquaint custom fields on any object are evaluated individually: fields with a direct Twenty equivalent (e.g., text-to-text, number-to-number) are mapped directly. Fields without a native equivalent are created as custom fields in Twenty's data model before the migration run. The field type is matched per Twenty's supported types: TEXT, NUMBER, SELECT, MULTI_SELECT, DATE, etc.

Acquaint's multi-branch model has no direct Twenty equivalent. If branches represent distinct legal entities, we recommend creating separate Twenty workspaces per branch. If they represent internal teams within one organization, we tag records by branch name using Twenty's tag system and note the original branch field for reference.

Acquaint workflows, sequences, and automated task rules do not migrate. These are platform-native logic constructs that require manual rebuild in Twenty's workflow builder. FlitStack AI exports a JSON representation of your Acquaint workflow definitions as a reference document for your Twenty admin.

Acquaint's built-in SMS and email templating features have no Twenty equivalent. Template bodies and merge-field syntax do not transfer. We export template names and content as a reference CSV for your team to recreate manually in Twenty or via an integrated email tool.

Acquaint's branded client portal with property access, document sharing, and viewing scheduling does not exist in Twenty. Client-facing portal data (documents, viewing schedules) can be preserved as Twenty Notes or custom objects with manual process for client re-onboarding. Your team will need to establish new communication workflows and potentially integrate a third-party portal solution if ongoing client access is required.