Migrate from Allegory to Freshsales

Allegory contacts migrate directly to Freshsales Contacts when the record includes an email address. Records without email require either a placeholder email (flagged for cleanup) or routing to the Freshsales Lead object. We validate email presence before migration and surface records needing resolution.

Allegory contacts that lack an email address cannot become Freshsales Contacts (Freshsales requires email on Contact records). We split these into Freshsales Leads, which accept phone-number-only records. A custom field flags the original Allegory record type for reconciliation. This routing ensures every Allegory contact reaches Freshsales, and the Source_Record_Type__c field preserves Allegory context for post-migration cleanup.

Allegory companies map 1:1 to Freshsales Accounts. Parent-company relationships use Freshsales' Parent_Account_Id field; circular references are flagged before migration. Industry pick-list values map value-by-value against Freshsales' predefined industry options. When an Allegory industry value has no direct Freshsales equivalent, we apply it as a custom text field on the Account record to preserve the original data without blocking migration.

Allegory deals migrate to Freshsales Deals with the deal name as Deal_Name, amount as Deal_Amount, close date as Expected_Close, and owner resolved by email match. Each Allegory deal stage name maps to a Freshsales stage value per pipeline. The deal amount, currency, and probability are preserved, and stage mappings are validated against Freshsales' pick-list options before migration to ensure every deal lands in the correct pipeline stage.

Allegory's pipeline concept maps to Freshsales' named Deal Pipelines. If Allegory uses a single pipeline with stage tags, we create one Freshsales pipeline and map those tags to stage names. For multi-pipeline Allegory setups, we create one Freshsales pipeline per Allegory pipeline.

Stage names map value-by-value from Allegory to Freshsales. For each pipeline in Freshsales, we create matching stage names and assign probability percentages and forecast categories from Allegory stage data. Stage-entered timestamps are preserved as custom datetime fields. This ensures deal forecasts in Freshsales reflect the same conversion likelihood as Allegory, and the timestamp history allows managers to analyze stage progression velocity and identify deals that stall at specific stages.

Allegory email logs become Freshsales Sales Activities of type 'Email'. Original timestamps, subject, body content, and owner email are preserved. Attachments are downloaded and re-uploaded as Freshsales Files linked to the activity. Email threading is maintained through the original message references, so follow-up emails in Freshsales show the complete conversation history and reps can view attachments without leaving the activity record.

Allegory call logs migrate as Freshsales Call Activities with call duration, disposition, and original timestamps. Owner resolution uses email match against Freshsales users; unresolved owners are flagged for admin assignment. Call disposition values are mapped to Freshsales Outcome options, and any Allegory disposition without a matching Freshsales option is applied as a custom field to preserve the original categorization.

Allegory meeting records become Freshsales Meeting Activities with start time, end time, title, and attendee list preserved. Meetings linked to a specific contact or deal carry the Freshsales association on migration. Location and conference bridge details are transferred to the Meeting Activity description field, and attendee email addresses resolve to Freshsales Contact records when matches exist.

Allegory notes map to Freshsales Notes attached to the corresponding Contact or Account record. Rich-text formatting is preserved where Allegory supports it; plain-text notes transfer as-is. The original note author and creation timestamp are stored as custom fields so the note attribution is visible in Freshsales, and any embedded images or file links are migrated as Freshsales File attachments.

Allegory custom objects require Freshsales custom object creation via the control panel or API before migration. We deliver a custom-object creation plan documenting the object name, field list, data types, and relationship to standard objects (Contact, Account, Deal). N:N relationships in Allegory map to Freshsales junction objects.

Allegory owner IDs resolve to Freshsales users by email address match. Unmatched owners are flagged before migration with a fallback-owner assignment option. The admin can either invite the owner to Freshsales first or designate a placeholder owner for their records.