Migrate from mQuest to Odoo CRM

mQuest contacts map directly to Odoo res.partner records with company_type set to 'person'. The primary company link in mQuest becomes partner_id on res.partner if the contact is a person within a company organization. Names are split into firstname and lastname, emails are normalized, and duplicate alerts are logged for review.

mQuest company records map to res.partner with company_type='company'. Odoo stores company VAT, website, and category_id on the same partner record used for contacts, so no separate company object exists in Odoo CRM. If a company has multiple locations, each location can be modeled as a child partner under the main company partner, preserving address details for each branch.

mQuest opportunities map to crm.lead records with type='opportunity'. The stage name from mQuest is looked up in Odoo's crm.stage table for the target crm.team and written as stage_id. Stage sequence order preserved for kanban display. If a stage does not exist, FlitStack AI creates it during schema setup, assigning a sequence number matching the original pipeline order.

mQuest lead records map to crm.lead with type='lead'. If mQuest does not distinguish leads from opportunities, all records default to type='lead' and are converted manually in Odoo using the built-in 'Convert to Opportunity' wizard after migration. You can schedule a bulk conversion in Odoo Studio for efficient processing.

mQuest stage names merge into existing Odoo crm.stage records per sales team. If a stage name does not exist in Odoo, a new crm.stage record is created during schema setup before data migration begins. Stage sequence numbers are assigned sequentially per team.

mQuest call logs with subject, duration, and notes migrate to crm.phonecall. The phonecall is linked to the corresponding res.partner or crm.lead via the partner_id and opporunity_id foreign keys. Original start datetime preserved in call_date. If the caller ID matches an existing partner email, the phonecall is automatically linked; otherwise it remains orphaned until manual assignment.

mQuest email records become mail.message entries on the res.partner or crm.lead's chatter thread. The message is stored with message_type='email', author_id set to the matched res.partner, and body containing the email HTML. Odoo's mail.thread automatically threads replies. Attachments in the original email are saved as ir.attachment records linked to the same mail.message, preserving file size and name.

mQuest meetings map to calendar.event records with start_datetime, stop_datetime, name, and attendee_ids resolved by email match to res.users. The event is linked to the related crm.lead or res.partner via the res_model and res_id fields. If an attendee email does not correspond to a res.users record, Odoo creates a placeholder partner record for that attendee, allowing visibility without login.

mQuest file attachments on contacts, companies, or deals re-upload to Odoo's ir.attachment table with res_model pointing to the target model (res.partner or crm.lead) and res_id set to the destination record ID. Odoo stores files in its filestore directory. If a file exceeds Odoo's 25 MB limit, FlitStack AI splits the upload into chunks and reassembles them on the server.

Any mQuest custom objects require a new Odoo model created via ir.model and ir.model.fields before migration. If mQuest exposes custom object metadata via API, FlitStack AI generates the Odoo model XML and applies it during schema setup. N:N associations in mQuest map to Odoo's x_xref intermediate tables.

mQuest owner IDs resolve by email match to res.users. Unmatched owners are flagged in the pre-migration report — the team either invites them to Odoo or assigns records to a fallback active res.users. Inactive users can own records in Odoo but cannot log in.

mQuest tags on contacts and companies map to res.partner.category (for partners) or crm.tag (for leads/opportunities). New category records created automatically if the tag name does not already exist in Odoo. Tags with special characters are sanitized, replacing spaces with underscores and removing punctuation to conform to Odoo's naming rules.