Migrate from OptifiNow to Microsoft Dynamics 365 Sales

OptifiNow uses a single Contact object with lifecycle-stage and status properties to track prospects through to customers. Dynamics 365 separates unqualified prospects into Lead and qualified buyers into Contact with a mandatory parent Account. We apply a lifecycle-stage routing rule during scoping: contacts below a defined qualification threshold (e.g., New, Open) map to Dynamics Lead; those at or above qualification (e.g., Attempting to Contact, Qualified) map to Dynamics Contact with a parent Account resolved from the OptifiNow Company record. The original OptifiNow lifecycle stage migrates to a custom field hs_original_lifecycle__c on both Lead and Contact for reporting continuity.

OptifiNow Company records map to Dynamics 365 Account. The primary address on the OptifiNow Company migrates to the Account's primary address fields. OptifiNow allows multiple addresses (invoice, delivery, primary) on a single company; Dynamics 365 permits only one primary address per Account entity, so we preserve the primary address and document secondary addresses in a custom multi-line text field for manual reconciliation by the customer's admin.

OptifiNow Opportunities map to Dynamics 365 Opportunities with Amount, Probability, Expected Close Date, and Description fields preserved. Pipeline stage names in OptifiNow are tenant-configurable and map to Dynamics Sales Process stage values, which we define during the discovery phase when the actual OptifiNow stage names are enumerated. OwnerId resolves via email match to a pre-provisioned Dynamics User.

OptifiNow exposes custom objects via API, but the schema is not publicly documented. We enumerate custom object types and their field definitions during the discovery phase by querying the live tenant's API. Each discovered custom object becomes a Dataverse custom entity with equivalent field types, lookup relationships to Contact, Account, and Opportunity, and validation rules. The destination schema is deployed to a Dynamics 365 sandbox for validation before any production custom-entity data migrates.

OptifiNow activity logs (calls, emails, meetings, social interactions, tasks) link to contacts and accounts. These migrate to Dynamics 365 as Task, Email, Appointment, and PhoneCall activity records. Call logs from any VOIP integration preserve duration and disposition in custom fields on PhoneCall. We set the Regarding field (regardingobjectid) to the parent Contact or Account record using the migration-time resolved ID. The full activity chronology is preserved by setting the actual Start Date/End Date on each activity to the original OptifiNow timestamp.

OptifiNow notes attach to contacts, companies, and opportunities. These migrate to Dynamics 365 as Annotation records linked via objectid and objecttypecode to the target Contact, Account, or Opportunity. Rich-text formatting is preserved; any embedded file attachments migrate as CRM cloud storage attachments.

OptifiNow User records include role assignments, territory assignments, and team memberships that affect pipeline routing. We map OptifiNow owner IDs to Dynamics 365 User records by email match. Any OptifiNow owner without a corresponding Dynamics User is flagged in the reconciliation queue before migration begins, because Opportunity and Contact inserts require a resolved OwnerId.

OptifiNow stores email sequences, triggers, delays, and branch conditions as internal workflow definitions that cannot be extracted as runnable automation packages. We extract sequence metadata (trigger conditions, step order, delay intervals, recipient filters) as a plain-text process map document. The customer's admin rebuilds sequences in Dynamics 365 via Power Automate or Sales Engagement standard tools. This limitation is disclosed at scoping so the customer can plan rebuild effort.

OptifiNow's content management module stores marketing collateral, social media materials, blogs, and images. File assets migrate as binary blobs to SharePoint or Dynamics cloud storage, but their approval workflow associations, scheduling metadata, and version history do not transfer. We document the content inventory and recommend that the customer's marketing team re-establish approval workflows in Microsoft SharePoint and Power Automate.

OptifiNow allows enterprises to define benchmark sales processes and workflow rules that are opaque and tenant-specific. We document the workflow map during discovery by walking the tenant's configuration UI and API. The documented process inventory is delivered as a written handoff for the customer's admin or a Dynamics 365 implementation partner to rebuild in Power Automate or Dynamics workflow designer. Process definitions do not migrate as executable logic.