Migrate from Devi to Zoho CRM

Devi's core function (social media high-intent lead detection) implies a Lead or contact record created when the platform identifies a prospect. We infer the existence of a Lead-like object storing profile data, detection source (LinkedIn post, Twitter/X mention, etc.), and intent score. We require the customer to provide a sample export or schema document before designing the Zoho Lead field mapping. The social media platform of origin becomes a custom Zoho Lead field, and any scoring data maps to a custom lead score field.

Devi's data model may store contact details separately from detected leads, but the research corpus contains no confirmation of a dedicated Contacts object. If the customer confirms contact records exist in Devi, we map them to Zoho Contacts with a deduplication strategy based on email address as the primary key. We require a schema sample from the customer to confirm field names and data types before migration design.

No evidence of a Companies or Accounts object in Devi's documentation. Given its narrow scope (social media lead detection), the platform may store company affiliation only as a property on the Lead record rather than as a separate object. If the customer confirms company-level records exist, we map them to Zoho Accounts using the company name as the primary deduplication key, with website and industry as secondary fields.

Deals are not mentioned in Devi's reviewed functionality, which focuses on lead detection rather than pipeline management. If the customer's workflow involves tracking opportunities derived from Devi leads, we map any deal records to Zoho Deals with the pipeline and stage configuration applied during migration design. We flag that Deals require a separate scope confirmation from the customer before migration begins.

No user management documentation surfaced for Devi. We require the customer to confirm the number of active users, their roles, and the email addresses associated with each user before migration. Zoho User records are provisioned by the customer's admin, and we resolve the mapping by email match during the migration phase.

Devi's lead detection likely logs timestamps and sources for each detected lead (e.g., LinkedIn comment, Twitter mention, Facebook interaction). These interaction events map to Zoho Tasks with ActivityDate set to the original interaction timestamp, subject describing the social platform and interaction type, and the lead's Zoho ID set as WhatId. We require a sample interaction export to confirm field structure.

G2 reviewers mention AI-generated visual content as a valued feature, implying a media or content asset object in Devi. If confirmed, we map these assets to Zoho Attachments linked to the related Lead or Contact record, with the original file preserved and any AI-generated caption or metadata stored as a Zoho Note. File type, storage location, and metadata schema require customer confirmation.

No evidence of a custom field system surfaced in the research corpus. If Devi supports custom fields on Lead or Contact records, we map them to Zoho custom fields during migration design, applying Zoho's field type constraints (text, number, picklist, date, etc.) and the 300-field-per-module limit. Customer-provided schema documentation is required before this phase.

No documented integrations with third-party platforms were found for Devi. If the customer has configured any outbound integrations (webhooks, Zapier, or native sync), we map the destination endpoint to Zoho Webhooks or a Zoho Connected App. Any custom API endpoints used by Devi integrations are documented in the handoff report for rebuild in Zoho.

No user management, roles, or permissions documentation was found for Devi. We request that the customer provide an inventory of user accounts, their access levels, and any team structures before migration. Zoho Roles and Profiles are configured during migration design, and the customer's admin approves the permission mapping before production migration.