Migrate your AllClients data

The primary object in AllClients. Exported as a flat CSV from the Data Migration menu, including all standard fields, email, phone, address, and owner assignment. We map each row directly to the destination Contact object.

Notes are exported as a separate Notes.csv file, not inline with the Contact CSV. We merge note content back into the Contact record as a custom multi-line field or as the destination platform's native notes/comments object using the contact's email or ID as the join key.

AllClients supports user-defined Custom Fields per account. The UpdateCustomFields API endpoint handles write operations. We discover all custom field definitions during scoping and map them to equivalent destination custom properties, handling field type differences (text vs. date vs. dropdown).

Tags are applied to Contacts and exported as comma-separated values within the contact record or as a separate tagging export. We preserve them as Tags on the destination Contact object. Multi-value tag fields are supported across all major destination CRMs.

Groups are logical collections of contacts built using Group Actions. They have no independent export — contacts are filtered by group membership during export. We capture group membership as a custom Contact property or as membership in a destination List/Segment object.

Workflows are automation sequences combining emails, text messages, tasks, tags, and other actions. AllClients does not export workflow execution state. We migrate Workflow definitions as inactive templates so they can be reviewed and reactivated in the destination platform. The trigger conditions (date-based, event-based) must be manually validated post-migration.

Email templates are stored under the Email Marketing section. We export them as HTML blobs and import them into the destination platform's template library. We preserve inline images as external URLs and flag any liquid-merge-tag syntax that requires conversion.

Campaigns represent scheduled email sends linked to contact segments. Campaign history (send dates, open rates) is metadata rather than a discrete object. We migrate campaign names and linked segments; the actual sending history is not portable.

Tasks are created within contact records or as part of Workflow sequences. We export task titles, due dates, and completion status as activity records. Completed tasks and future-scheduled tasks map differently depending on destination support for historical vs. future-dated task objects.

Available on Premium and Elite tiers but not exposed via API export. Landing page content, form fields, and submission data cannot be programmatically extracted. We skip these objects and flag them during scoping so the customer can plan manual re-creation in the destination platform.

Attachments are associated with individual Contact records. We download files from AllClients storage and re-upload them to the destination CRM's attachment storage. Large binary files are chunked to stay within migration timeouts. We preserve the contact-to-attachment relationship via record ID mapping.

AllClients accounts have a defined set of users. The user list is small (1–2 on base plans) but we capture Name, Email, and role/permissions so Owner assignment on Contact records can be remapped to the destination system's user accounts.