Migrate from RAYNET CRM to Odoo CRM

RAYNET Contact records map to Odoo res.partner with type=contact. We preserve RAYNET's lifecycle stage as a custom selection field (x_raynet_lifecycle_stage) since Odoo CRM's crm.lead model derives stage from the opportunity pipeline rather than the contact. RAYNET's GPS coordinates (latitude/longitude auto-derived from address for Map Analysis) migrate to custom float fields x_latitude and x_longitude on res.partner because Odoo CRM does not auto-compute these from addresses. Standard name, email, phone, street, city, and country fields map 1:1.

RAYNET Account records also map to res.partner with type=company. During scoping we identify whether the RAYNET Account and Contact share a single parent record or are separate entities, and design the Odoo partner hierarchy accordingly. Company-type partners get child contact partners linked via child_ids. Address fields (shipping, billing) migrate to partner address fields with dedicated contact address records.

RAYNET Deals map to Odoo crm.lead records with type=opportunity. The RAYNET pipeline maps to an Odoo crm.team, and RAYNET pipeline stages map to Odoo stage_ids within that team's stage sequence. Deal value, probability, estimated close date, and owner migrate to crm.lead fields expected_close_date, planned_revenue, user_id, and team_id. Closed-Won and Closed-Lost stages map to Odoo's won and lost stage states.

RAYNET activity records (Calls, Emails, Meetings) map to Odoo mail.activity records linked to the migrated res.partner or crm.lead via res_id and res_model. Activity type (call, email, meeting) maps to Odoo's activity_type_id, with duration preserved in Odoo's date_deadline and note fields for call disposition. Email subject and body migrate as note body text.

RAYNET Sales Orders map to Odoo sale.order records. Order lines migrate as sale.order.line records with product, quantity, unit price, and taxes. The linked Account maps to the Odoo res.partner partner_id, and the associated Deal maps to the crm.lead origin_id if the customer enables the CRM-Sales integration in Odoo. Shipping and billing addresses migrate as partner shipping contact records.

RAYNET Quotes with validity dates and line-item pricing map to Odoo sale.order records in draft or sent state. Quote validity dates migrate to sale.order validity_date. Line items migrate as sale.order.line records with product, description, quantity, and unit price. If the Quote was signed, we attach a note indicating the signed status and copy any signature metadata as a custom field x_signed since Odoo handles e-signatures via external integrations.

RAYNET custom fields on Contact and Account objects migrate to Odoo res.partner custom fields. We extract the custom field schema via RAYNET list export, map each field to the equivalent Odoo field type (char, selection, date, float, integer), and pre-create the fields in Odoo via Odoo Studio or data migration script before import. Fields without a direct Odoo equivalent store as x_raynet_cf_{fieldname} char fields for admin review.

RAYNET Users map to Odoo res.users by email match. We extract every distinct owner_id on Contact, Account, Deal, and Activity and resolve against the destination Odoo instance's users list. Any RAYNET Owner without a matching Odoo User enters a reconciliation queue for the customer's Odoo admin to provision before record import proceeds. Inactive RAYNET owners map to Odoo inactive users with a flag in x_raynet_owner_active.

RAYNET Tags on Contacts and Deals migrate to Odoo res.partner.category (tags) for partner records and crm.lead tag_ids for opportunity records. We extract all distinct tag values, create the corresponding Odoo tag categories, and re-associate them during import. If Odoo tag limits are a concern at scale, we alternatively map tags to a custom multi-select Char field for admin review.

RAYNET pipeline stage names, order, and probabilities map to Odoo crm.stage records within each crm.team. We extract the full stage configuration including stage colors (if set) and map probabilities to Odoo's probability field. If RAYNET has multiple pipelines (ENTERPRISE tier), each becomes a separate crm.team in Odoo with its own stage sequence. Stage count limits are not a constraint in Odoo at any tier.

Files attached to RAYNET Contacts, Accounts, Deals, and Activities export via RAYNET XLSX export cross-referenced with the record list. We export the file references and URLs, then upload attachments to Odoo ir.attachment records linked via res_model and res_id to the migrated res.partner or crm.lead. Attachment re-association uses the cross-reference ID map built during scoping.

RAYNET Automation rules (conditions, triggers, and actions at the Builder and Architect tier) are stored in a RAYNET-specific format with no documented export endpoint. We identify every active automation rule during scoping and deliver a written inventory listing each rule's trigger object, conditions, actions, and Odoo Workflow or automated action equivalent. The customer's Odoo admin rebuilds these post-migration. Skipping this step leaves business processes unautomated in the new platform.