Migrate from Simpleview CRM to Pipedrive

Simpleview Member Accounts map to Pipedrive Organizations. Standard fields (name, address, phone, website) map directly. The AcctID from Simpleview is preserved as a custom field sv_acct_id__c for reference. Organizations are created first in the import sequence so that Person records and Deals can reference them via lookup. Multi-department portal views from Simpleview do not have a Pipedrive equivalent; we document the department breakdown for manual reconfiguration post-migration.

Contact roles on Member Accounts in Simpleview map to Pipedrive Person records linked to the Organization via the organization_id field. Each distinct contact role (primary, billing, sales) becomes a separate Person with a custom field sv_contact_role__c. Primary contact flag maps to a boolean custom field sv_primary_contact__c. We resolve the organization reference at migration time so that Persons insert with a valid parent Organization ID.

Simpleview Listings represent member directory entries tied to Member Accounts via AcctID. Pipedrive has no native Listing object, so we store listing attributes as custom fields on the parent Organization: sv_listing_id__c, sv_category__c, sv_offer_text__c (rich text), sv_redeem_start__c, sv_redeem_end__c, and sv_post_start__c. Multi-select amenities from Amenity_MS are extracted, deduplicated, and mapped to Pipedrive Labels during import. We flag any Listing without a matching AcctID for manual account association.

Simpleview Coupons link to both ListingID and AcctID with date ranges (RedeemStart, RedeemEnd, PostStart, PostEnd) and HTML OfferText. Since Pipedrive has no Coupon object, we store coupon metadata as custom fields on the Organization: sv_coupon_id__c, sv_offer_text__c, sv_redeem_start__c, sv_redeem_end__c, sv_post_start__c, and sv_post_end__c. HTML content in OfferText is stripped to plain text during transform to avoid rendering issues in Pipedrive's text fields.

Simpleview Events are first-class objects with Cvent and Eventbooking integrations. We map Events to Pipedrive Deals using an Event Record Type so that event-specific fields (event date, venue, attendee count) appear on the Deal page layout. The Simpleview Event-to-Attendee association migrates as Person records linked to the Event Deal, with a custom field sv_attendee_event_id__c tying each Person to the parent Event Deal. Event categories (meetings, sports, conventions) become Pipedrive pipeline labels or stage prefixes.

Simpleview Opportunities across all four DMO pipelines (meetings, sports, travel trade, group business) map to Pipedrive Deals. Pipeline stage definitions are collected during discovery and reconstituted as Pipedrive stages under a matching Deal Record Type. Stage names, probabilities, and order migrate from Simpleview. Closed-Lost and Closed-Won reasons map to Pipedrive Deal loss_reason and a custom sv_original_stage__c field.

Simpleview custom fields under FieldCategory Custom_Account are non-standard and vary per client. We extract the complete field definition set during the audit phase, generate a client-specific field map, and create equivalent custom fields in Pipedrive before migration. Field types are resolved (text, number, date, picklist) and mapped to Pipedrive field types. Fields that cannot map (complex formulas, cross-object references) are flagged for manual review.

Amenity_MS stores multi-select amenity values using a client-defined vocabulary. We extract the full vocabulary during discovery, deduplicate it, and create Pipedrive Labels for each unique amenity. At migration time, each Listing's amenity values are assigned as Label matches against the created vocabulary. Unmapped amenity values are flagged for manual review before final import. The available vocabulary may exceed Pipedrive's label limits on lower tiers; we flag this during scoping.

Simpleview DAM stores documents against Member Accounts or Events. We extract file references via the Simpleview API where accessible, download files within the migration window, and re-upload as Pipedrive Files attached to the parent Organization or Deal. File metadata (created date, file type, original URL) is preserved in a custom field sv_source_url__c on the File. Files exceeding Pipedrive's attachment size limits are flagged for alternative storage (S3, Google Drive) with a link stored in a custom field.

Simpleview CRM engagement records (calls, emails, meetings, tasks) link to Member Accounts or Events. These map to Pipedrive Activities attached to the Organization or Deal. Call duration, disposition, and subject migrate to custom activity fields. Email body migrates as activity content. Meeting date, time, and location migrate to activity fields. Task status and due date migrate directly. Activity timestamps are preserved to maintain the historical timeline sequence.

Simpleview Extranet stores partner co-op campaign signups, enrollment records, and payment data as action records. These do not have a direct Pipedrive equivalent. We extract the underlying account and listing associations and store co-op campaign metadata (campaign name, enrollment date, status) as custom fields on the Organization. Enrollment workflows and portal access records do not migrate; we document them for manual rebuild in Pipedrive or an alternative partner portal tool.