Migrate from Simpleview CRM to Microsoft Dynamics 365 Sales

Member Accounts are the primary organizational object in Simpleview CRM and map directly to Microsoft Dynamics 365 Sales Account. Standard fields (account name, address, phone, website) migrate as typed Account fields. The destination OrganizationID relationship in Simpleview may map to a custom Account field or a Territory if the DMO operates multiple regional member groups. We create the Account before any related Contact or Listing import to satisfy the AccountId lookup.

Simpleview Member Accounts can carry multiple contact-person records (primary, billing, event contact). These map to Dynamics Contacts with the parent AccountId lookup resolved at migration time. Email address is used as the dedupe key; duplicate contacts by email are flagged for the customer's admin to resolve before final import. The primary contact flag in Simpleview becomes the Primary Contact checkbox on the Account's contact subgrid.

Listings represent partner or member entries in the directory and are tied to Member Accounts via AcctID. Dynamics has no native Listing equivalent, so we create a custom sv_Listing__c entity with fields for listing name, category, description, location, and a lookup to the Account record. Amenity_MS multi-select arrays are stored as a delimited custom text field and can be split into a related sv_ListingAmenity__c junction entity if the customer's reporting requires amenity-level filtering.

Coupons link to both ListingID and AcctID, with date ranges (RedeemStart, RedeemEnd, PostStart, PostEnd) and category metadata. We create a custom sv_Coupon__c entity with lookup relationships to the Account and the sv_Listing__c custom entity. OfferText may contain HTML markup; we strip HTML tags during import and store plain text, flagging any hyperlink references for the customer's admin to re-embed in Dynamics if needed. Expired coupons (PostEnd in the past) are migrated with a status flag for archival rather than active use.

Events in Simpleview CRM are first-class objects with registrations tied to Members. Dynamics Event is used for calendar and meeting tracking but has limited registration management compared to Simpleview's Cvent and Eventbooking integrations. We migrate Event name, date, location, description, and registrant counts. Registration-level detail (attendee name, ticket type, dietary requirements) maps to custom sv_EventRegistration__c records with a lookup to the Event and the Account or Contact. If the DMO uses Cvent for registration, those records do not migrate and are flagged for rebuild in Cvent natively post-migration.

Simpleview CRM pipelines cover meetings, sports, travel trade, and group business with DMO-specific stage names. We extract the customer's current pipeline stage definitions during discovery, then configure Microsoft Dynamics 365 Sales Record Types and Sales Processes that replicate the pipeline structure. Each pipeline becomes a Record Type; each stage becomes a StageName value with probability mapped from Simpleview. Closed-Lost and Closed-Won states from Simpleview carry forward as the terminal stages.

Fields under the Custom_Account and Custom_Account_MS categories are defined per organization and have no standardized schema. We extract all custom field definitions during the audit phase, generate a client-specific field map, and resolve each field to a typed Dynamics custom field (text, number, date, picklist, or checkbox) before migration. Fields with no clear destination mapping are flagged for the customer's admin to categorize as new custom fields or as Notes attached to the Account.

Amenities on Listings use a client-defined vocabulary with multi-select arrays (Amenity_MS). The destination vocabulary does not exist until we create it. We extract the full source amenity set, deduplicate it, and present a mapping table where each source amenity maps to a destination tag, picklist value, or custom sv_ListingAmenity__c record. Unmapped amenities are flagged for manual review before final import. If the destination Dynamics org already has a tag taxonomy (Topics, for example), we map to that instead.

Simpleview CRM owners on Member Accounts, Listings, Events, and Opportunities map to Microsoft Dynamics 365 Sales User records by email match. Any Simpleview owner without a corresponding Dynamics User is placed in a reconciliation queue, and the customer's admin provisions the missing User before record import resumes. Owner reassignment during migration (for staff who have left) is handled by the admin's decision on whether to map to an active replacement or to a generic migration service account.

Simpleview DAM handles digital assets, and documents may be stored against Member Accounts or Events. We extract file references and, where API access permits, download and re-upload assets to the destination's SharePoint-integrated ContentDocument library tied to the Account or custom Event entity. Files that cannot be accessed via the Simpleview API are flagged with URL references so the customer's admin can manually transfer them post-migration.