Migrate from AllClients to Salesforce Sales Cloud

AllClients does not have a separate Lead object; all records are Contacts. We apply a qualification split during migration: Contacts with a deal association, assigned sales owner, or explicit qualification flag map to Salesforce Contact attached to an Account. Contacts without those indicators map to Salesforce Lead. We preserve the original AllClients contact ID in a custom field allclients_contact_id__c on both Lead and Contact for reconciliation.

For AllClients Contacts that qualify as Salesforce Contacts (existing deal or explicit qualification), we create Salesforce Contact records attached to Accounts. The Account is either created from the AllClients contact's company name or resolved against an existing Account if a match by name or domain exists. AccountId resolution is the critical dependency step before Contact insert.

AllClients does not have a standalone Account object; company data lives on the Contact record. We extract distinct company names from AllClients Contact records and create Salesforce Account records as a parent lookup table before importing Contacts. Company address fields on the AllClients Contact map to the Account BillingAddress.

AllClients exports Notes as a separate Notes.csv file with a contact reference (email or ID). We join Notes.csv to the main Contact export using email as the matching key, then create Salesforce Note records linked via ContentDocumentLink to the parent Contact or Lead. If a contact email changed between exports, the join produces orphans that we flag for manual review.

AllClients Custom Field definitions are discovered during scoping via the account settings export. Each AllClients custom field maps to a Salesforce custom field of the equivalent data type (text, number, date, picklist, checkbox). We pre-create the Salesforce custom fields in the destination org before migration. Multi-select picklists in AllClients map to Salesforce multi-select picklist fields.

AllClients Tags are comma-separated values on the Contact record. We map them to a Salesforce custom multi-select picklist field (preferred for CRM filtering) or to Salesforce Topics with TopicAssignment records (preferred for reporting). The customer chooses the strategy during scoping. We do not map Tags to the standard Salesforce Tags object because it is deprecated for most orgs.

AllClients Groups are logical contact collections with no independent export. We capture group membership by filtering the contact export by each group's criteria, then store group names as a custom multi-select picklist value on the Contact record. This preserves the group semantics without requiring a separate custom object.

AllClients Workflows do not export execution state or enrollment records. We capture the workflow definition (triggers, conditions, delays, email and task actions) as a written specification and recreate it as an inactive Salesforce Flow. The customer or their Salesforce admin enables and adjusts the Flow post-migration. Contacts already enrolled in AllClients workflow sequences will not carry their enrollment status.

AllClients Email Templates export as HTML blobs from the Email Marketing section. We import them into Salesforce as Salesforce Classic Email Templates or Lightning Email Templates depending on the customer's destination org type. Inline images export as external URLs and are re-hosted or linked by reference. We preserve template name and subject for reuse in Salesforce Flow email actions.

AllClients Campaigns represent scheduled email sends linked to contact segments. Campaign history (send dates, open rates) is metadata that does not export as a discrete object. We migrate campaign names and linked contact segments to Salesforce Campaign records with the segment contacts added as CampaignMembers. Send and open rate metadata is noted in the handoff document for manual reporting reconstruction.

AllClients Tasks created within contact records or workflow sequences export as rows in the main contact CSV with task title, due date, and completion status. We create Salesforce Task records linked to the parent Contact or Lead. Completed tasks preserve their Completed status; future-scheduled tasks preserve their due date. Overdue tasks from AllClients do not carry a Salesforce reminder date automatically; we map the AllClients due date to Salesforce ActivityDate.

AllClients file attachments associated with Contact records are downloaded from AllClients storage and uploaded to Salesforce as ContentVersion records. Each file receives a ContentDocumentLink to the parent Contact or Lead record. Large binary files are chunked to avoid timeout during upload. We preserve the original filename and file type metadata.

AllClients user lists are typically small (1-2 on base plans). We capture Name, Email, and role assignment from the user export. Owner assignment on AllClients Contact records maps to Salesforce OwnerId by resolving the owner's email against the destination org's User table. Users without a Salesforce User match go to a reconciliation queue for admin provisioning before Contact import.

AllClients Landing Pages and Popup Forms are Premium and Elite tier features with no API export. We skip these objects and flag them in the handoff document as requiring rebuild in Salesforce Experience Cloud, Web-to-Lead, or a third-party form tool. Form submission history does not migrate.