Migrate from Simpleview CRM to Twenty CRM

Member Accounts are the primary organizational object in Simpleview CRM, analogous to Companies in Twenty. Standard fields (name, address, contact info) map directly. Custom_Account fields (client-defined, non-multi-select) map to custom fields on the Twenty Company object. We extract the full Custom_Account field set during audit, create matching typed fields in Twenty Settings → Data Model before import, then import Member Account records as Company records. The Simpleview AcctID is preserved as a custom field sv_acctid__c for audit and cross-reference.

Simpleview Listings represent partner/member entries in the directory and are tied to Member Accounts via AcctID. Listings have amenity arrays (Amenity_MS), category assignments, and coupon associations that have no direct Twenty standard object equivalent. We create a Listing custom object in Twenty with fields for amenity tags, category, listing URL, and the foreign key to the parent Company record. Amenity values from the client-defined vocabulary are deduplicated, mapped to Twenty Tags or a multi-select picklist, and any unmapped values are flagged for manual review before final import.

Coupons in Simpleview link to both ListingID and AcctID with date ranges (RedeemStart, RedeemEnd, PostStart, PostEnd) and HTML body text (OfferText). We map Coupon records to Note objects in Twenty linked to the target Company (via AcctID resolution), with custom fields for coupon code, validity dates, and category metadata. The OfferText HTML body is stored as Note body text. Coupon-to-listing associations are preserved as a custom relationship field on the Note pointing to the mapped Listing custom object.

Simpleview Events are first-class objects with integrations to Cvent, Eventbooking, and Meetingmax. Event registrations link to Member Accounts. We create an Event custom object in Twenty with fields for event name, date range, venue, registration status, and a link to the primary Company (destination organization). Individual registrations migrate as child records via a registration sublist or as Note records attached to the Event, depending on registration field complexity. Event-to-attendee associations are sequenced after Company import so that the AcctID lookup resolves at migration time.

Simpleview CRM pipelines cover meetings, sports, travel trade, and group business with DMO-specific stages that vary by organization. Pipeline stages migrate as Opportunity Stage values in Twenty. Each Simpleview pipeline becomes a Twenty Opportunity with a custom stage field set to match the customer's current pipeline. We collect the customer's pipeline stage definitions during discovery and create the matching stage picklist in Twenty before migration. Closed-Won and Closed-Lost reasons map to custom Opportunity fields.

Multi-select custom fields under Custom_Account_MS use a client-defined vocabulary and are often used for amenity classification, membership tier, or partner capability tagging. We extract the full vocabulary, deduplicate it, and map each value to either a Twenty multi-select picklist (if under 150 values) or a set of Tags (if over 150 unique values). Any unmapped vocabulary values are flagged in a review report before the final import batch runs.

Simpleview DAM handles digital assets stored against Member Accounts or Events. We extract file references and, where Simpleview API access permits, download files and re-upload them to Twenty as File records attached to the relevant Company, Listing, or Event record. If the Simpleview DAM is inaccessible via API (requires portal session), we extract the file reference URLs and deliver a file migration inventory for manual re-upload or a separate DAM migration engagement.

The Simpleview Extranet stores partner-submitted enrollment, co-op campaign signups, and online payments as action records rather than static data. We extract the underlying account and listing associations as Company records and Note entries capturing co-op campaign participation and enrollment status. The portal login credentials, session data, and enrollment workflows do not migrate; we document the Extranet feature set for the customer to assess against Twenty's access control capabilities or a replacement partner portal.

Simpleview CRM stores activity history against Member Accounts and Events including tasks, notes, and calendar entries. We map Simpleview activity records to Twenty Task (for action items), Note (for observations and call logs), and Event (for scheduled meetings) objects. Each activity record is linked to the parent Company record resolved via AcctID at migration time. We preserve the original Simpleview timestamp in the activity record for timeline ordering.

Simpleview users assigned to records (account owner, opportunity owner, task assignee) map to Twenty WorkspaceMembers. We match by email address. Any Simpleview Owner without a matching Twenty user goes to a reconciliation queue; the customer provisions the missing WorkspaceMember before record import resumes. Inactive Simpleview users map to inactive Twenty members if historical assignment must be preserved.