Migrate from RAMM to Odoo CRM

RAMM contacts map to Odoo res.partner records. The partner type (customer, vendor, or both) is set based on RAMM contact classification. Email, phone, address, and job title fields transfer directly. If RAMM stores a lifecycle stage, the contact routes to crm.lead in addition to res.partner.

RAMM contacts that have a deal or lifecycle stage value (New, Working, Qualified, Customer) split into Odoo crm.lead records. The RAMM stage value maps to an Odoo stage_id by name lookup in the target pipeline. Unmapped stage names are flagged for pipeline pre-configuration before migration.

RAMM company records map to Odoo res.partner with partner_type='company'. Company name maps to name; domain maps to website; industry maps to industry_id; employee count maps to employee_count; annual revenue maps to revenue. Address fields (street, city, country) map to the corresponding Odoo partner address fields.

RAMM deal records map to Odoo crm.lead. Deal name becomes name; amount becomes expected_revenue; close date becomes date_deadline; owner resolves by email match to Odoo res.users. Pipeline from RAMM maps to Odoo team_id; RAMM stage name maps to stage_id within that team.

RAMM pipeline definitions become Odoo crm.team records. Each team has its own set of stage records in crm.stage with name, sequence, and probability. Teams are matched by name; missing teams are created during migration setup. Stage sequence order is preserved from RAMM.

Stage names map value-by-value from RAMM to Odoo stage names. Where RAMM stage names differ from Odoo target stage names, a value-mapping table specifies the translation. Stage probability and onglet (legend color) are carried over. Stage-entered timestamps are stored as Char fields in Odoo since stage history is not natively preserved.

RAMM custom properties require pre-creation in Odoo as ir.model.fields before migration. Field names convert from RAMM camelCase to Odoo snake_case. Field types are mapped: text to text, number to float, date to date, select to selection. Selection option values must be pre-defined in Odoo. We deliver a custom-field creation plan as part of the migration package.

RAMM activity history (logged calls, sent emails, meeting notes) migrates as Odoo mail.message records linked to the corresponding crm.lead or res.partner. Subject maps to subject; body maps to body; date maps to date; owner resolves by email match to res.users. Attachments download from RAMM and re-upload to Odoo's ir.attachment.

RAMM file attachments on contacts, companies, or deals download from RAMM storage and upload to Odoo ir.attachment linked to the migrated record. File name and content are preserved. Odoo's default file size limit is 25MB per attachment; files exceeding this are flagged for manual handling.

RAMM owner and user records resolve by email match to Odoo res.users. Where RAMM users have no matching Odoo user by email, records are assigned to a fallback Odoo user and flagged in the pre-migration audit report. Your team creates Odoo user accounts for unmatched owners before the full migration run.

RAMM workflow rules, sequences, and automation triggers do not have an Odoo equivalent that can be imported. These must be rebuilt using Odoo Studio (action rules, automated actions) or Python server actions. FlitStack exports RAMM workflow definitions as a reference document for your Odoo admin to use during the rebuild phase.