Migrate from Fello to Microsoft Dynamics 365 Sales

Fello contact records map 1:1 to Dynamics 365 Sales Contact rows. Every standard contact property (name, email, phone, address) maps to its Dataverse equivalent. Owner resolution matches Fello owner email against Dynamics 365 user principal names — unmatched owners are flagged before the full run.

Fello Company records become Dynamics 365 Sales Account rows through a direct object mapping. The Company primary-contact link maps to the primary ContactId on the Account record, establishing the relationship between companies and their main contacts. Fello's multi-address model, which distinguishes between billing and shipping addresses, maps to the Address1 and Address2 composite fields in Dataverse, preserving all address variations during the migration.

Fello records marked with a status of 'unqualified' or 'new inquiry' route to the Dynamics 365 Lead entity during migration. Lead status pick-list values are mapped value-by-value to align with Dynamics 365's default Lead Status options, which include New, Contacted, Qualified, and Lost. This ensures that all Fello lead statuses are correctly translated to their corresponding Dynamics 365 statuses, maintaining the lead lifecycle state throughout the transition.

Fello's 0–100 AI lead score has no native equivalent in Dynamics 365 Sales. We create a custom number column (Fello_LeadScore__c) on the Contact table and migrate the score value for every contact. Probability of close can optionally be seeded from this score using a formula column.

Every Fello custom property on a contact becomes a custom column in Dynamics 365 Sales Enterprise. The API name uses the new_ prefix (e.g., new_PropertyAddress__c for real-estate address fields). Custom columns must be created in the target Dynamics environment before the migration validates field existence.

Fello company-level custom fields such as mls_number and listing_status map to custom columns on the Dynamics 365 Sales Account table. Unlimited custom columns are available in Enterprise licensing, making it ideal for complex data structures. However, the Professional tier limits custom columns to 15 per table, so it is important to plan your field mapping carefully to avoid exceeding this limitation during migration.

Fello engagement logs map to the corresponding Dynamics 365 Sales activity entities. Email activities become Email (activitypointer) records; calls become PhoneCall; meetings become Appointment; notes become Note. Original timestamps and owner links are preserved via custom datetime columns since Dynamics 365 sets CreatedOn at insert time.

Fello automation rules (trigger conditions, drip sequences, outreach triggers) do not migrate to Dynamics 365 Sales. We export each automation definition as a JSON reference document and deliver it to your Dynamics admin so Power Automate flows can be rebuilt using the original Fello logic as a specification. This is the most time-intensive part of any Fello migration.

Fello sync logs and plugin-state flags (e.g., last_sync_timestamp, enrichment_source) have no Dynamics 365 Sales equivalent. We preserve these as custom columns on the Contact record (e.g., Fello_SyncTimestamp__c) for audit purposes, but they do not drive any Dynamics behavior after migration.

Fello-branded email templates, consent language, and TCPA proof-of-consent records are Fello-native constructs. Dynamics 365 Sales does not have a comparable consent-tracking model. We export consent records as a CSV for manual re-entry into Dynamics consent fields or Power Automate tracking.

Fello owner IDs are resolved to Dynamics 365 Sales SystemUser records by email match. If a Fello owner has no corresponding Dynamics user, their records are assigned to a fallback owner specified in the migration plan. Owner history (who owned a contact historically) is preserved in a custom lookup column on the Contact record.

Fello contact tags and segments have no direct Dynamics 365 Sales equivalent. We migrate each tag as a separate custom column on the Contact record (e.g., new_FelloTag_MLS_Seller__c as a two-option field) so reporting can filter on the original Fello segmentation after migration.