Migrate from Ringy (formerly iSales) to Odoo CRM

Ringy Leads are the primary record object and the only object with a documented CSV export path. The UI Generate CSV function supports filtering and an Include all custom fields checkbox. We extract all Lead fields including name, phone, email, address, status, source, and any custom properties. Ringy Lead status values map to Odoo CRM stage names or a dedicated state field. We preserve the original Lead ID in a custom Char field for audit traceability. Any auto-blocked records identified during scoping are flagged separately and imported into a dedicated Odoo Lead queue for manual review rather than silently discarded.

Company records in Ringy are not exported via a separate path; they are extracted from Lead CSV rows where a company name field is populated. We normalize these into Odoo CRM Contact records with is_company=True and parent_id left null. The company name becomes the Contact name field, and any company-level address data is mapped to the contact address fields. If Ringy has a separate Companies section with dedicated fields, we request a filtered export of that subset and map it to Odoo Partner records. Ringy custom fields on companies are preserved as Odoo custom Char or selection fields on the Partner model.

Ringy Contact records are exported via the same Lead CSV export workflow, since Ringy conflates Leads and Contacts in a single record model. We extract contact-level fields (name, phone, email, custom properties) and map them to Odoo CRM Contact with is_company=False. Email addresses serve as the dedupe key during import. Any associated parent company is resolved by matching the Ringy company name against the previously migrated Contact (is_company=True) records and linked via parent_id. Custom fields on contacts migrate as Odoo custom fields on the res.partner model.

Deals in Ringy are associated with Leads and included in CSV exports via filtering. Pipeline names and stage definitions are preserved as metadata during extraction. We map each Ringy pipeline to an Odoo CRM pipeline with corresponding stage sequences, configuring Odoo stages to match Ringy stage names and ordering before migration begins. Deal amount, close date, owner, and associated Lead reference migrate directly. Closed-won and closed-lost statuses from Ringy map to Odoo CRM Won and Lost stage values. Any Ringy custom fields on Deals migrate as Odoo custom fields on crm.lead.

Call, email, and SMS activity history embedded in Ringy Lead records migrates as Odoo CRM Mail Thread messages attached to the corresponding Lead or Opportunity. Activity timestamps, types (call, email, sms), disposition data, and notes transfer to mail.message records with message_type set accordingly. Call duration and disposition migrate to custom fields on the message record. Activity ordering is preserved by setting create_date to the original Ringy timestamp. Note: Call recordings and full SMS thread content are not accessible via any documented export path and are flagged as non-migratable in the inventory document.

Custom fields on Ringy Leads must be explicitly included during CSV export via the Include all custom fields checkbox. We verify this option is selected during extraction scoping. Each Ringy custom field is analyzed by data type (text, number, date, picklist) and mapped to the equivalent Odoo CRM field type (Char, Float, Date, Selection). Picklist values from Ringy become Selection field options in Odoo. We pre-create all custom fields in Odoo via Settings before any data import begins. Any Ringy custom fields that cannot be mapped (e.g., unsupported data types) are documented and migrated as Char fields with original values preserved for later reclassification.

Tags applied to Ringy records are extracted from Lead CSV rows where tag values appear in a delimited column. Tags are mapped to Odoo CRM Tags (crm.tag), which are a standard Odoo CRM feature. Multiple comma-separated Ringy tags on a single record become multiple Tag records linked via crm.lead.tag.rel. We preserve the full original tag taxonomy during migration so that the customer's admin can reorganize tagging logic in Odoo post-migration. If Ringy uses a taxonomy or hierarchical tag structure, we document it in the migration inventory for manual rebuild in Odoo.

Ringy owners referenced on Leads, Companies, and Deals are extracted by email from the CSV export. We resolve Ringy owners by email match against the destination Odoo CRM User records. Any Ringy owner without a matching Odoo User is held in a reconciliation queue for the customer admin to provision before record import resumes. Owner resolution must complete before Deal and Lead migration begins because Odoo CRM Opportunity requires an assigned user. Inactive Odoo users can be provisioned with no login access to preserve historical assignment without granting active licenses.

Ringy Lead status values (new, contacted, qualified, lost, converted) map to Odoo CRM stage sequences. We configure Odoo stages to match Ringy status labels and ordering before migration. Each stage probability percentage from Ringy is applied to the corresponding Odoo stage. Stage configuration is deployed via Odoo data import before any record migration begins. If the customer uses Ringy status values that do not map directly to Odoo stage concepts, we propose a mapping during scoping and document the rationale.

Ringy deal pipeline names and stage sequences are preserved as metadata during CSV extraction. We create corresponding Odoo CRM pipelines with matching stage sequences before migration begins. Each Ringy pipeline maps to a separate Odoo CRM pipeline view in the Kanban interface. Pipeline configuration is deployed via Odoo Settings before any Opportunity records are imported. If the customer has a single Ringy pipeline, we create one Odoo pipeline; multiple Ringy pipelines each become separate Odoo pipelines, which is a native Odoo CRM feature.

Drip campaigns and automated follow-up sequences in Ringy are stored as platform-native automation objects with no documented export API. Campaign structure, sequence logic, timing rules, and branching conditions cannot be extracted programmatically. We document the visible campaign structure including campaign names, associated stages, sequence templates, and keyword triggers as reference metadata in the migration inventory. The customer admin uses this document to rebuild equivalent automation logic in Odoo Studio using Odoo CRM's planned actions and server actions, or engages an Odoo partner for custom Python module development.

Call history, disposition data, and recording URLs stored in Ringy's built-in VOIP softphone are not accessible via any documented export mechanism or API. The CSV export for Leads surfaces call activity as timestamped history entries but does not include recording URLs or full disposition metadata. We extract any call data that appears in the Lead activity log and migrate it as mail.message records, but recording files and detailed call metadata are non-migratable. We document the call log gap in the migration inventory so the customer understands what is not transferred before migration begins.