Migrate from Allegory to Salesforce Sales Cloud

Allegory contacts with status marked as 'Prospect' or 'Unqualified' map to Salesforce Lead. The Allegory contact's primary company association migrates as a text field (Company__c) on the Lead record until an Account record exists to link via lookup. If the Company__c value exceeds 255 characters it is truncated and flagged for review.

Allegory contacts with status marked as 'Customer', 'Active', or 'Closed Won' map to Salesforce Contact. The Allegory contact's primary company must first be created as a Salesforce Account before the Contact can be linked via AccountId lookup. If the company does not yet exist, a placeholder Account is created and the Contact is flagged for later reconciliation.

Allegory company records map directly to Salesforce Account records. The Account.Name field maps from Allegory company.name. Salesforce Account requires the Name field—companies with no name are assigned a placeholder and flagged for manual review. Any missing industry or website values are migrated as blank and recorded in the data quality log.

Allegory parent-child company relationships map to Salesforce Account.ParentId. The parent company Account must be created before the child, or circular references are flagged and the child is attached to a root-level placeholder account. All hierarchical depths are preserved, and the migration audit includes a parent chain report.

Allegory deal records map to Salesforce Opportunity. The Opportunity.Name maps from Allegory dealname, Amount maps from deal.amount, CloseDate maps from closedate, and StageName maps from dealstage using value-by-value mapping configured per record type. Any Allegory custom deal fields become custom Opportunity fields (__c) with appropriate data type conversion.

Allegory pipeline identifier maps to a Salesforce RecordTypeId. Each Allegory pipeline requires a corresponding Salesforce Record Type created in Setup before migration. The Sales Process is then associated with the record type to scope stage pick-list values correctly. Record type developer names are derived from the pipeline name with underscores replacing spaces.

Allegory call, email, and note activities map to Salesforce Task records. The Task.Subject is set from the Allegory activity type (e.g., 'Outbound Call', 'Email Sent'), Task.ActivityDate from the timestamp, and Task.OwnerId from owner resolution by email match. If the owner email does not resolve to a Salesforce User, the Task is assigned to a migration fallback user and logged for later reassignment.

Allegory meeting records map to Salesforce Event with StartDateTime and EndDateTime preserved from the source. The Event.WhatId links to the related Opportunity or Account, and Event.WhoId links to the related Contact or Lead if applicable. If the related record does not exist in the target org, the Event is stored with a custom reference field and flagged for manual linking.

Allegory file attachments re-upload to Salesforce as ContentDocument (Lightning) or Attachment records. Files under 25MB use Attachment; larger files are uploaded to Salesforce Files (ContentDocument/ContentVersion) with the original filename preserved. The migration process records the ContentVersion checksum and links each file to its parent record via the LinkedEntityId.

Allegory owner resolved by email match against Salesforce User records. Unmatched owners are flagged pre-migration; your team either creates Salesforce users first or assigns records to a fallback user designated before migration runs. The fallback user is recorded in the migration log, and post-migration the owner field can be updated via a bulk reassignment script.

Allegory custom objects map 1:1 to Salesforce custom objects. Custom object relationships in Allegory that use a junction model map to Salesforce junction objects (custom __c objects with two lookup fields) if the relationship is many-to-many. The junction object name is derived from the two related objects concatenated, and field-level security is applied per profile after migration.

Allegory custom properties that have no Salesforce standard field equivalent become custom fields on the appropriate Salesforce object. The __c suffix is appended, spaces are removed, and character limits (40 for API name) are enforced during mapping. Custom field metadata (label, type, help text) is generated from Allegory field definitions and reviewed by the admin before deployment.