Migrate from Devi to Freshsales

Devi's high-intent lead detection implies person-level records with name, social handle, and engagement signals. We treat these as Freshsales Contacts with a discovery-phase schema confirmation required. Any inferred social media identifiers map to a custom text field devi_social_handle__c. Email address, if present, maps to the standard Email field on Contact. If Devi's records include company affiliation, we split to Account with the AccountId resolved before Contact insert.

Devi's social listening may capture company signals (employer, brand mentions). If company data is present in Devi's export, we map to Freshsales Account with Website, Industry, and Phone preserved. Account is created before Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert. If no company data exists in Devi's export, we create a default Account placeholder to attach person-level contacts.

Devi's core value proposition is identifying high-intent leads on social media. We infer a lead-scoring or intent-signal field that maps to Freshsales Lead with a custom field devi_intent_score__c carrying the original signal value. Lead Status maps to a Freshsales Status field with values defined during scoping. If Devi's records are already qualified (Contact-stage), we map directly to Freshsales Contact instead of Lead.

G2 reviewers mention AI-generated visual content as a Devi feature. If exported assets include image URLs, file references, or asset metadata, we store these as ContentDocument records linked via ContentDocumentLink to the parent Contact or Lead. If the asset count is high and the customer needs a structured content library, we pre-create a custom Asset__c object with Name, Type, URL, and OwnerId fields before migration.

Devi may include user seat records or assigned owner information on lead entries. We match by email against the Freshsales destination User table. Any Devi User without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status is preserved in a custom field devi_user_status__c.

Devi's lead detection runs on a schedule, producing timestamped events (lead identified, intent signal triggered). These migrate to Freshsales Task records with Subject, ActivityDate, and description preserved. The Task maps to the parent Contact or Lead via WhoId. We do not migrate social media message content as Freshsales EmailMessage records unless Devi's export includes full message bodies in a structured format.

Devi's data model is unconfirmed. We allocate discovery time during Phase 1 to receive the customer's Devi export (CSV preferred), identify all columns, infer data types, and map each to a Freshsales standard or custom field. Custom fields in Freshsales are created as __c fields on the relevant object before any data import begins. We validate field types (text, number, date, picklist) against Freshsales API constraints before migration.

Social media lead tools commonly use tags to segment by platform (Twitter, LinkedIn), intent level, or content type. If Devi's export contains tag columns, we map to Freshsales multi-select picklist fields on Contact or Lead. Tag values are preserved as individual picklist entries, and the migration validates that total tag string length does not exceed Freshsales' 40,000-character field limit.