Migrate from Devi to Microsoft Dynamics 365 Sales

Devi's G2 review mentions high-intent lead detection as the core feature, suggesting a Lead concept exists. Whether Devi uses a single Contact object with a lifecycle stage property or a separate Lead object is unconfirmed. We begin discovery by requesting the customer provide a Devi data export or screen-share walkthrough of the record structure. If Devi uses a single Contact-like object, we apply a split rule during migration: records flagged as unqualified prospects map to Salesforce-style Lead; records tied to an Account or marked as customers map to Contact under an Account. We preserve any intent score, lead source, or social signal metadata as custom fields on the Microsoft Dynamics 365 Sales record.

Devi's social selling focus may not include a formal Companies or Accounts object — the platform may track company context as a property on the Lead or Contact rather than a separate entity. We confirm this during discovery. If a Companies entity exists, it maps 1:1 to Microsoft Dynamics 365 Sales Account with the domain or company name as the dedupe key. If no separate Companies entity exists, we extract company context from Lead or Contact records and create Account records during migration to establish the relational model required by Microsoft Dynamics 365 Sales .

Devi's AI-generated visual content feature implies a content or media asset object exists within the platform. The schema (file types, metadata, storage location) is unconfirmed. During discovery we identify whether assets are stored within Devi or referenced externally, and confirm whether they can be exported as files. If a file export is available, we map assets to Microsoft Dynamics 365 Sales Note records with attachments or to SharePoint Document Library via the native SharePoint integration. If assets cannot be exported programmatically, we document the content inventory for the customer to manually migrate or link post-migration.

Devi's high-intent lead detection generates social signals (engagement scores, platform sources, intent flags) that have no native Microsoft Dynamics 365 Sales equivalent. We map these to custom fields on the Lead or Contact object (devi_intent_score__c, devi_social_source__c, devi_first_engagement_date__c) after confirming which Microsoft Dynamics 365 Sales edition the customer is licensing. Custom fields are available from the Professional tier ($65/user/mo) and above. We deploy the custom field schema to a Sandbox org before production migration.

No user management documentation surfaced for Devi. Seat counts, roles, and admin capabilities are unverified. During discovery we request a list of active Devi users from the customer. If a user list is available, we match by email against the destination Microsoft Dynamics 365 Sales org's User table. Any Devi user without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

No integrations with third-party platforms were documented for Devi. We do not migrate integration logic because none was found. We document any Devi integration the customer identifies during discovery and provide a written recommendation for equivalent Microsoft Dynamics 365 Sales integration via AppExchange, Power Automate, or native Microsoft 365 connectors.

No workflow, automation, or sequence system was documented for Devi. We do not migrate automation logic because no such system was found in the research corpus. We work with the customer during discovery to identify any informal automation they have built within Devi (filters, rules, alerts) and document them for manual reconstruction in Microsoft Dynamics 365 Sales Flow by the customer's administrator post-migration.

No evidence of a custom field system was found for Devi. During discovery we request the customer provide a full field inventory from their Devi instance or confirm that no custom fields are in use. Any custom fields identified migrate to equivalent custom fields on the corresponding Microsoft Dynamics 365 Sales entity, with API names matching the Devi field names where characters allow and a __c suffix per Microsoft Dynamics 365 Sales convention.