Migrate from Less Annoying CRM to Microsoft Dynamics 365 Sales

LACRM Contact records map directly to Microsoft Dynamics 365 Sales Contact. LACRM's standard fields (name, email, phone, address, tags) map to the corresponding Dataverse Contact columns. Custom contact fields migrate as typed custom columns. LACRM's 31-digit UIDs are stored as strings throughout the migration pipeline to prevent float rounding that would silently break record matching and foreign key relationships. Contacts are imported after Account so that the parent AccountId reference is satisfied at insert time.

LACRM Company records map to Microsoft Dynamics 365 Sales Account. LACRM maintains Companies as distinct objects rather than embedding company data inside Contact records, so we import Account first and use it as the parent for every Contact. The LACRM relationship table linking Contact to Company becomes the Dynamics 365 AccountId lookup on Contact. We validate that every Contact-Company relationship is preserved as an AccountId reference after import completes.

LACRM Pipeline Items map to Microsoft Dynamics 365 Sales Opportunity. LACRM pipeline stages are free-text and fully customizable per account; we map them to a Microsoft Dynamics 365 Sales Process with picklist StageName values that we configure before migration. Each LACRM pipeline becomes a Dynamics 365 Opportunity Record Type with its own Sales Process so that stage values stay scoped per line of business. Closed-Lost and Closed-Won dates and any custom pipeline fields migrate to Opportunity custom columns.

LACRM custom fields exist on Contacts, Companies, and Pipeline Items. We map them by name and type: LACRM text fields become Dataverse single-line text, number fields become decimal or whole number columns, date fields become datetime columns, and dropdowns become choice columns with the original option labels preserved. We pre-create the destination column schema before any data import so that field types are locked before migration begins.

LACRM tags applied to Contacts or Companies migrate as a custom column on Contact or Account. We recommend a multi-select picklist for tag migration when the tag count is below 150; above that threshold we use a text column with comma-separated values. The customer chooses the tag strategy during scoping based on how tags are used for segmentation in the destination.

LACRM Notes attached to Contacts, Companies, or Pipeline Items migrate as Dynamics 365 Annotation records with their timestamp, author, and body content preserved. The Annotation is linked to the parent Contact, Account, or Opportunity via the ObjectId reference. Rich text formatting in LACRM Notes is preserved where the content is HTML; plain text Notes migrate as-is.

LACRM Tasks associated with Contacts or Pipeline Items migrate as Dynamics 365 Task records with their due date, assignee, completion status, and linked Contact or Opportunity reference intact. Open tasks migrate as open; completed tasks migrate with their CompletedOn timestamp. Task subjects and descriptions map directly to the Task Subject and Description columns.

Calendar events (meetings, calls) logged against Contacts migrate as Dynamics 365 Appointment records with their timestamp, title, description, and linked Contact reference intact. StartTime, EndTime, and Location are preserved. Attendees are not migrated as separate records since Dynamics 365 Appointment Attendee is a separate entity with different semantics from LACRM's event participant model.

Files attached to LACRM Contacts or Companies are exported as base64-encoded content and re-created in Dynamics 365 as SharePoint document locations linked to the Account or Contact record. We use the Dynamics 365 SharePoint integration (enabled per-entity in the destination) to create the document location records and upload the file content. Where SharePoint is not available in the destination environment, files attach to the Annotation entity instead.

LACRM user accounts, names, email addresses, and permission levels migrate as Dynamics 365 User records. LACRM's role model is simple (admin vs. standard user); we map this to the Microsoft Dynamics 365 Sales role structure with a custom security role created during scoping to match LACRM's two-tier permission model. We resolve LACRM owner references by email match against the destination User table and flag any owners without matching Users for manual provisioning.