Migrate from Simpleview CRM to Odoo CRM

Member Accounts are the primary organizational record in Simpleview CRM and map to Odoo Contact (with is_company=True for organizational accounts) or Company records. Standard fields including name, address, contact information, and status map directly. Custom_Account fields transfer to custom contact fields on the Odoo res.partner model, with FieldCategory resolved per client during the audit phase. The AcctID from Simpleview is preserved as an external reference field for reconciliation. We create Contacts before any related Listings or Event registrations so that cross-references are satisfied at load time.

Simpleview Listings represent partner entries in the member directory and map to Odoo Product records. The ListingID becomes an external reference field. Listing name maps to Product name; category assignments map to Odoo product categories or tags. Amenity_MS multi-select data requires vocabulary extraction, deduplication, and mapping to Odoo tags or product attributes before import. If a Listing is tied to a specific Member Account (AcctID), we resolve the Odoo Contact reference at migration time using the AcctID-to-contact mapping built during the Member Accounts phase.

Coupons link to both ListingID and AcctID with date ranges (RedeemStart, RedeemEnd, PostStart, PostEnd) and category metadata. The OfferText body may contain HTML. We migrate coupon records as custom Odoo records using the crm.lead model with custom fields for coupon metadata, or as Product variants with specific pricelists depending on the customer's use case. HTML content in OfferText is stripped to plain text for the description field. The redemption date window maps to custom date fields in the Odoo record.

Simpleview CRM pipelines cover meetings, sports, travel trade, and group business with DMO-specific stage definitions. Odoo CRM uses a single pipeline with default stages (New, Qualified, Proposal, Negotiation, Won, Lost). We configure custom stage values on the CRM Lead model to match the customer's existing Simpleview pipeline, preserving stage probabilities and order as custom stage fields. Stage mapping is collected during discovery. The Opportunity AcctID maps to the CRM Lead partner_id contact reference at migration time.

Simpleview Events are first-class objects with attendee registrations and integrations to Cvent, Eventbooking, and Meetingmax. We migrate event records as Odoo CRM Leads with custom fields capturing event_name, event_date, venue, and attendee_count sourced from the Simpleview event object. Attendee registrations (member-to-event linkages) map as separate CRM Lead records linked to the primary event record via a custom event_registration_id field, or as CRM Lead Line items if the customer uses Odoo's crm.lead.product mechanism. Native Cvent and Meetingmax integrations are not migratable and are documented in the integration-rebuild inventory.

Attendee records linked to Events carry the member's AcctID and event-specific registration metadata (registration date, session selections, dietary preferences). We create secondary CRM Lead records for each attendee registration, linking to the parent event CRM Lead via a custom lookup field. Member AcctID resolves to the migrated Odoo Contact. Registration metadata maps to custom fields on the attendee Lead record.

Non-multi-select custom fields defined on Member Accounts carry a FieldCategory of Custom_Account and have no standardized schema across clients. We extract the full field definition during the audit phase, including field type, picklist values, and conditional visibility rules, then pre-create equivalent custom fields in Odoo developer mode before migration. Custom_Account_MS multi-select fields map to Odoo many2many_tags or custom selection fields depending on value cardinality. Every custom field is resolved individually against the destination schema during mapping.

Amenities on Listings use a client-defined vocabulary and are multi-select (Amenity_MS). The available amenity vocabulary is unique per Simpleview organization and may not align with Odoo's default product category taxonomy. We extract the full Simpleview vocabulary, deduplicate it, and map each value to the nearest Odoo product tag (product.tag) or product.attribute.value. Any amenity values that cannot be mapped are flagged in a reconciliation report for manual review before the final import. HTML-encoded amenity labels are decoded during the transform phase.

Simpleview DAM handles digital assets stored against Member Accounts or Events. We extract file references from the Simpleview API and, where API access permits, download and re-upload binary assets to the Odoo ir_attachment table linked to the migrated res.partner or crm.lead record. If the Simpleview API does not expose binary attachment downloads, we migrate file reference URLs as external URL fields on the Odoo record and flag the attachment for manual re-upload post-migration.

The Simpleview Extranet stores partner-submitted enrollment forms, co-op campaign signups, and online payment records. These are action records with Simpleview-specific form logic and co-op campaign workflow state that do not have direct Odoo equivalents. We migrate the underlying account and listing data (which is the factual substrate of the portal records) and flag co-op campaign and enrollment action records as manual-reentry candidates in the migration report. Partner contact credentials do not transfer to Odoo Portal access, which requires separate user provisioning.

Simpleview CRM Owner records map to Odoo res.users. We resolve owners by matching the Simpleview owner email against the Odoo destination User table. Any Simpleview Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status on the Simpleview Owner carries into a custom field owner_active__c on the Odoo User record for reference.

Simpleview DMO pipelines define stages specific to the customer's tourism sales process: meetings, sports, travel trade, and group business. Each pipeline has its own stage sequence with probabilities. We configure Odoo CRM Lead stage values to match the customer's existing stage definitions, preserving stage order, probability percentages, and the pipeline association in a custom field source_pipeline__c on each Lead. Stage mapping is collected during discovery and applied as an Odoo stage configuration before the production migration runs.

Simpleview CRM records carry create_date, modify_date, and often last_modified_by timestamps that reflect the full history of record changes. We map these to Odoo's mail.message records on the relevant res.partner or crm.lead model, using mail.message with model, res_id, and date fields to preserve the original timestamp. If the customer requires a full audit trail including the modifying user, we capture modify_date in a custom field last_modified_date__c on each record.