Migrate from Simpleview CRM to HubSpot

Simpleview Members map directly to HubSpot Companies. The MemberId becomes a custom property (Simpleview_Member_ID__c) for traceability and to enable delta-run deduplication on subsequent migrations. Custom_Account fields from Simpleview translate to HubSpot custom company properties, stripping the FieldCategory prefix. Primary contact assignment uses HubSpot's primary company association.

Simpleview Contacts map 1:1 to HubSpot Contacts. The Contact's MemberId lookup resolves to a HubSpot Company ID after the Member-to-Company migration completes. Email is the primary deduplication key. Contacts without a primary MemberId attach to a default HubSpot company or are flagged for manual review.

Simpleview Listings store rich partner-attraction data with amenity fields. HubSpot has no native listing object. At Sales Hub Professional and above, we create a HubSpot custom object named Listing with properties mirroring Simpleview's listing attributes. At lower tiers, Listing data collapses into Company properties or a structured property group on the Company record.

Simpleview Event records track group business, conventions, and sports tournaments with venue, date, and bid-status fields. HubSpot has no native event concept. We create a HubSpot custom object named Event with event_type, venue_name, bid_status, and expected_attendees as properties. Alternatively, Events map to HubSpot Deals with a custom event_type property group when custom objects are not available in the current HubSpot tier.

Simpleview Coupon records track partner co-op offers with redemption dates and categories. We create a HubSpot custom object named Promotion mapping CouponID, AcctID, RedeemStart, RedeemEnd, OfferTitle, and OfferText to equivalent custom properties. Redemption status is tracked via a custom pick-list field updated through HubSpot workflows post-migration.

Every non-multi-select custom field in Simpleview with FieldCategory = Custom_Account creates a corresponding HubSpot custom property on Company. We strip the prefix, convert FieldName to snake_case, and infer the property type (text, number, date, pick-list) from Simpleview's data type. Multi-select fields (Custom_Account_MS) become HubSpot multi-checkbox properties.

Simpleview Amenity fields (amenity checkboxes per listing) map to HubSpot multi-checkbox properties on the Company or Listing custom object. Amenity_MS fields create HubSpot multi-checkbox properties; single-select Amenity fields create HubSpot single-checkbox boolean properties named after the amenity label. All amenity property names are derived from the Simpleview FieldName value, converted to snake_case.

Simpleview owner assignment is stored per record. We resolve Simpleview owner email addresses against HubSpot user emails. Unmatched owners are flagged and assigned to a fallback HubSpot owner. Owner history is preserved as a custom text property (Original_Owner_Email__c) for audit purposes.

Simpleview file attachments on Member or Contact records are downloaded and re-uploaded to HubSpot Files, associated to the corresponding Company or Contact record. File size limits apply per HubSpot tier. Inline images in notes are extracted and rehosted as HubSpot file attachments.

Simpleview workflow definitions — event-service triggers, bid-stage automations, and membership renewal sequences — do not migrate. We export Simpleview workflow definitions as a structured JSON reference document so your HubSpot admin can rebuild them in HubSpot's workflow builder. Automation logic tied to DMO-specific field categories must be translated manually.