Migrate from Simpleview CRM to Nutshell

Simpleview Member Accounts are the primary organizational object and map to Nutshell Company as the primary record. Standard fields (account name, address, phone, website) map directly to Nutshell Company fields. Primary contacts on the Member Account become Nutshell Person records linked to the Company via the Person's Company field. Multi-department portal data (sales vs marketing vs events views) does not map natively; we consolidate into a single Company record and note the department scoping as a manual review item for the customer to reassign access in Nutshell.

Listings represent partner or member entries in a directory tied to a Member Account via AcctID. Nutshell has no Listings object. We create a custom object called Partner_Listing__c in Nutshell (available on Pro and above) with fields for listing name, category, description, and amenity multi-select. If the customer is on Nutshell Foundation (which does not include custom objects), we store Listing data as tags on the parent Company record and use the Notes field for amenity descriptions. Amenity_MS multi-select values require vocabulary mapping since the DMO-defined amenity taxonomy will not match Nutshell's tag vocabulary.

Simpleview CRM pipelines cover meetings, sports, travel trade, and group business with DMO-specific stage names. Nutshell Deal stages are generic (typically: Prospect, Presentation, Proposal, Negotiation, Won, Lost). We collect the customer's current pipeline stage definitions during scoping, map each to the nearest generic Nutshell stage, and flag any DMO-specific stage semantics that will be lost. The destination Deal record type and stage configuration happens before migration so that imported Opportunities land in the correct stage immediately.

Events are first-class objects in Simpleview CRM with attendee registrations and integrations to Cvent and Eventbooking. Nutshell has no event registration object. We create a custom object called Event__c in Nutshell (Pro tier or above) with fields for event name, date, location, attendee count, and registration status. Attendee associations link to the related Company or Person record via lookup. Event registration status fields are recreated as picklists on the custom object. Event registrations that existed as separate records in Simpleview become Event__c records with registration data stored as related child records.

Coupons in Simpleview CRM link to both ListingID and AcctID with date ranges (RedeemStart, RedeemEnd, PostStart, PostEnd) and HTML OfferText. Nutshell has no coupon or offer object. On Pro and above we create a Coupon__c custom object with fields for coupon name, offer text (migrated as plain text, HTML stripped), start date, end date, and lookups to the partner Listing and Member Account. On Foundation we store coupon metadata in a Note attached to the related Company record. Any HTML in OfferText is stripped to plain text during migration.

Fields under Custom_Account and Custom_Account_MS are defined per-organization and have no standardized schema across Simpleview CRM clients. We extract the full custom field definition set during the audit phase, generate a client-specific field map, and provision each field as a typed custom field on the Nutshell Company or Person object before migration begins. Multi-select custom fields become Nutshell multi-select picklists; date fields become date pickers; numeric fields become number fields. Any custom field that cannot be typed into a Nutshell native field is flagged for manual review.

Documents stored against Member Accounts or Events in Simpleview DAM are extracted via the API where file reference access is available. We download files and re-upload them to the corresponding Nutshell Company or Person record as native file attachments. If the Simpleview DAM API does not expose file content directly, we extract file names, URLs, and metadata and flag these records for manual re-upload by the customer's admin team.

The Simpleview Extranet stores partner-submitted enrollment records, co-op campaign signups, and online payment transactions as action records rather than static profile data. These records are tied to the Member Account but do not have a clean structural equivalent in Nutshell. We migrate the underlying account data (enrollment status, co-op campaign participation flags, payment history summary) as fields on the Company record and flag the full Extranet action log as out of scope for the migration. The customer receives a written inventory of Extranet records for manual re-creation or replacement with a partner portal tool.