Migrate from Simpleview CRM to Freshsales

Simpleview Member Accounts are the primary organizational object and map to Freshsales Account for organization-level data (address, industry classification) and a primary Contact for the main member representative. The Account Name maps from the Simpleview AcctName; the primary Contact derives from the primary contact fields on the Account. Any Custom_Account fields attach to both Account and Contact custom field blocks, and we resolve the field types (text, number, date, picklist) during the audit phase before schema deployment.

Listings represent partner or member directory entries tied to a Member Account via AcctID. The destination mapping is a scoping decision: we create either a custom Listing object with lookup to Account and fields for amenity arrays, category assignments, and coupon associations, or we land Listings as Contacts with a rich custom field block and a tag-based amenity structure. The customer chooses during scoping. Amenity_MS values use a client-defined vocabulary that we extract, deduplicate, and map to Freshsales Tags or a multi-select picklist.

Coupons link to both ListingID and AcctID with date ranges (RedeemStart, RedeemEnd, PostStart, PostEnd) and category metadata. We map Coupon to Freshsales Deal with the coupon OfferText stored in the Deal description or a custom field. Start and end dates migrate to Deal custom fields; status (active, expired, redeemed) maps to Deal stage. Coupon body text (OfferText) may contain HTML and we strip formatting before import.

Simpleview Events map directly to Freshsales Event with standard fields for title, description, start and end dates, location, and venue. Cvent and Eventbooking integration data on the Event record migrates as custom fields. Event registrations (attendee-to-event links) migrate as EventRelations or as Tasks with custom event-type fields, depending on the complexity of the registration data in the source.

Simpleview Opportunity records represent pipeline entries for meetings, sports, travel trade, and group business. These map to Freshsales Deals, with the pipeline stage mapped to the Freshsales deal stage. Multi-pipeline setups (common in Simpleview) require a scoping decision: if Freshsales Growth or above, we can create multiple pipelines; otherwise, pipeline is encoded in a custom Deal field. Closed-won and closed-lost reasons migrate to custom fields.

All custom fields under the Custom_Account and Custom_Account_MS field categories have no standardized schema — each client's set is unique. We extract every field definition (name, type, picklist values) during the audit phase, generate a client-specific field map, and pre-create each field in Freshsales under the Contacts or Accounts module before any record import. The field type must be resolved individually: text fields to text, numeric fields to number, date fields to date, multi-select to multi-select picklist.

Amenity_MS is a multi-select vocabulary defined per client on Listings. The available amenity values are not standardized and change between organizations. We extract the full vocabulary from the source, deduplicate the value list, and map each term to a Freshsales Tag or a multi-select picklist field on the Listing/Contact destination. Unmapped values are flagged for manual review before the final import pass.

Documents stored against Member Accounts or Events in Simpleview DAM may be extractable via API or file reference. We download accessible files and re-upload as Freshsales Attachments linked to the corresponding Account, Contact, or Event record. Files that are only accessible via the Simpleview Extranet portal and cannot be retrieved via API are flagged in the handoff package with instructions for manual download before account closure.