Migrate from LockedOn to Microsoft Dynamics 365 Sales

LockedOn contacts map directly to Dynamics 365 Contact records. The primary company association migrates as AccountId lookup. LockedOn contact properties like buying criteria and tags become custom fields on the Contact record. These custom fields are defined during schema provisioning and preserve the original contact data integrity.

The LockedOn agency or company record maps to Dynamics 365 Account. Parent-child agency hierarchies in LockedOn translate to Account.ParentAccountId relationships in D365. We also map any secondary addresses, agency type classifications, and custom agency-specific fields to matching Account attributes. This ensures that multi-branch agencies maintain their structural hierarchy in the target environment and that each branch is linked to its parent through the standard parentaccountid reference.

LockedOn property records have no direct equivalent in Dynamics 365 Sales. We create a custom RealEstateProperty table in Dataverse with fields for address, listing status, price, property type, and listing agent — mapped field-by-field from LockedOn's property schema, including geospatial coordinates for mapping integration.

OFI schedules are a core LockedOn concept tracking inspection times, attendee lists, and feedback. These map to a custom RealEstateOFI table linked to RealEstateProperty via a lookup relationship. The OFI table also stores recurring schedule flags, inspection type classifications, and any attached media references for historical audit trails.

QR check-in and manual OFI registration records map to a custom OFIAttendee table with attendee name, contact link, check-in timestamp, and feedback notes — linked to the parent OFI record. Each attendee entry also records whether they confirmed attendance via SMS, email, or in-person, preserving the original registration source.

LockedOn deals representing property transactions map to Dynamics 365 Opportunity. The deal amount, stage, and close date transfer directly. Deal status values map to Opportunity StageName pick-list via value mapping. We also map custom deal attributes such as property condition rating and marketing source to custom fields on the Opportunity for complete historical context.

LockedOn task plans and triggers automate follow-ups, OFI reminders, and welcome sequences. These must be rebuilt in Power Automate. We export LockedOn workflow definitions as JSON so your Dynamics admin can reference the logic during rebuild. The exported JSON includes trigger events, conditions, and action steps for accurate replication.

LockedOn vendor portal reporting data — seller updates, inspection summaries, days-on-market stats — transfers as Notes attached to the parent Property record plus custom fields on RealEstateProperty for structured metrics. These notes retain the original author, timestamp, and any attachments, ensuring full auditability of vendor communications.

LockedOn logged calls, emails, and meetings map to their corresponding Dynamics 365 Activity types. Original timestamps, owners, and regarding (parent record) links are preserved. Activity subjects and descriptions are transferred verbatim, and any custom activity attributes are mapped to custom fields on the activity entity for completeness.

LockedOn bulk communication templates and email blasts do not transfer. Email templates can be exported as HTML text for manual recreation in Dynamics 365's template system. The exported HTML preserves inline styles, images, and merge tags, allowing your team to reconstruct the visual layout and personalization fields within D365's template editor.

LockedOn uses tags to categorize contacts (buyer, seller, investor, etc.). Tags migrate as a multi-select custom field on Contact so filtering and segmentation work in Dynamics 365. We preserve the original tag names and map them to the new field's picklist values, ensuring no categorization data is lost during migration.

LockedOn agency staff records resolve against Dynamics 365 SystemUser by email address. Unmatched staff are flagged — records can be assigned to a fallback owner or the user invited to D365 before migration commits. This resolution step ensures data ownership continuity and supports compliance with security policies throughout the migration.