Migrate from Road Runner to Odoo CRM

Road Runner contacts flagged as 'company' type map directly to Odoo res.partner with company=True. Address fields (street, city, state, zip, country) split into Odoo's five-field address schema. Email, phone, and website preserved. Industry requires a custom field or category tag since res.partner has no native industry pick-list.

Road Runner contacts flagged as 'contact' type map to Odoo res.partner with company=False and parent_id pointing to the associated company partner. Job title stored in the function field. Mobile and direct phone map to partner.phone and partner.mobile respectively as needed.

Road Runner contacts without a primary company link route to Odoo crm.lead rather than res.partner, since Odoo requires a partner_id for contact records. Email, phone, name, and custom properties carry over. The creating sales rep resolves to user_id by email match against res.users.

Road Runner deals map to Odoo crm.lead records with type='opportunity'. Deal name becomes crm.lead.name; amount maps to planned_revenue; expected close date maps to date_deadline. Stage names map to Odoo crm.stage records by value lookup — each Road Runner stage must have a corresponding Odoo stage pre-created in the target pipeline.

Road Runner pipelines map to Odoo crm.team records; each pipeline's stages map to crm.stage records within that team. Stage probability, next_step, and fold status are native stage attributes that Road Runner may not have equivalents for — these default based on Odoo stage configuration or get mapped from Road Runner's stage probability data if available.

Road Runner tasks with a project association map to Odoo project.task records. Task name, description, assigned user (resolved by email), due date, and stage/status map directly. Tasks without a project association map to crm.lead activity records (mail.message) instead as needed.

Road Runner activity records (call logs, email logs, notes) map to Odoo mail.message records on the parent crm.lead or res.partner. Message type is set to 'email' for email activities, 'comment' for notes, and 'notification' for internal call logs. Original timestamps preserved; author resolved by email to res.users.

Road Runner custom properties on any object require pre-migration Odoo custom field creation. FlitStack creates Char, Text, or Selection fields depending on data type. Multi-select or complex pick-list custom properties may need custom widget configuration or intermediary many2many relations in Odoo.

Road Runner users are matched to Odoo res.users records by email address. Unmatched owners are flagged before migration — the team either invites them to Odoo first or assigns their records to a fallback user. No record lands without a valid Odoo owner assignment.

Road Runner file attachments on records are downloaded and re-uploaded to Odoo ir.attachment. Each attachment record includes res_model (the target Odoo model) and res_id (the target record ID) for correct linking. Binary file content is stored in Odoo's filestore; original filenames and create dates preserved.

Road Runner tags applied to contacts, companies, or deals map to Odoo crm.tag records. Tags are de-duplicated during migration — identical tag names collapse to a single crm.tag record and are linked via the crm.lead.tag_ids many2many relation for reporting purposes.

Road Runner equipment or asset records do not have a native Odoo CRM equivalent. If the Maintenance module is activated, equipment maps to maintenance.equipment with installation date and location. Otherwise, equipment references migrate as custom fields on crm.lead for reporting continuity.