Migrate from Moskit to Odoo CRM

Moskit Contact records map to Odoo res.partner with partner_type=contact. The Moskit contact's associated Company link maps to res.partner with parent_id pointing to the mapped Company partner. Email, phone, mobile, function, and website fields migrate directly. Custom contact properties migrate as Odoo custom fields via Studio or a custom module. We use the contact's email address as the Odoo partner dedupe key.

Moskit Company records map to Odoo res.partner with partner_type=company and is_company=True. Company address fields (street, city, state, country, zip) migrate to Odoo's address fields. The Company's CNPJ/CPF tax ID field maps to res.partner's vat field if populated. Custom company properties migrate as Odoo custom fields. The Company record must be created before any linked Contact so that parent_id is satisfied at import time.

Moskit Deals map to Odoo crm.lead with type=pipeline (Odoo's Opportunity). The deal's monetary value maps to Odoo's expected_revenue and stage probabilities map to Odoo's stage_id with the probability auto-calculated or set manually per stage. Deal owner (responsável) maps to Odoo's user_id by email match. Closed-Won and Closed-Lost reasons from Moskit custom fields map to Odoo's lost_reason or a custom field.

Moskit pipeline stages map to Odoo crm.stage records within the destination CRM team. We configure stage names, sequence order, and probability percentages to match Moskit's stage definitions. Each stage is assigned to the relevant Odoo sales team so multi-pipeline setups (if present in Moskit Professional) map to Odoo's multiple sales teams each with their own stage pipeline.

Moskit Activities (tasks, calls, meetings, notes) map to Odoo mail.activity records linked to the target res.partner or crm.lead via res_model and res_id. Activity type (call, meeting, task) maps to Odoo's activity_type_id. Timestamp fields (date, duration) migrate directly. Description and notes migrate as Odoo's note field. The responsible user maps by email match.

Moskit Projects are deal-spawned and carry a Negócio reference. We migrate Projects as Odoo project.project records with a custom field x_moskit_deal_id storing the source deal ID. After Deal migration, we run a lookup pass to update x_moskit_deal_id with the destination crm.lead ID so the linkage is preserved and queryable in Odoo. Project tasks migrate as project.task records under the parent project.

Moskit custom fields on Contacts, Companies, Deals, and Activities are discovered per object during extraction (no bulk schema endpoint in Moskit). We create equivalent Odoo custom fields via Studio or a custom module before migration. Field types (text, number, date, picklist, checkbox) map to the closest Odoo field type. Picklist options migrate as selection values or many2one relations depending on complexity.

Moskit Users map to Odoo res.users by email address match. We export all active and inactive Moskit users. Inactive Moskit users become Odoo res.users with active=False so they can be reactivated by the admin post-migration. Access rights and groups in Odoo are assigned during the approach phase based on the user's Moskit role, but the customer admin reviews and approves group assignments before they take effect.

If Moskit Professional or Enterprise has multiple deal pipelines, we configure multiple Odoo crm.team records (sales teams) each with their own pipeline stages. Each crm.team maps to a distinct stage sequence. Single-pipeline Moskit instances map to a single crm.team with the stages configured under it.

If Moskit Products are used in Deals (line items), they migrate to Odoo product.template. Product name, SKU (hs_sku equivalent), list_price, and standard_price migrate directly. Product categories map to Odoo's product.category hierarchy.

Moskit WhatsApp conversation metadata (timestamps, participant numbers, message count, deal association) migrates as Odoo mail.message records or note.note records linked to the Contact res.partner. Actual message content cannot migrate because it lives in WhatsApp Business API infrastructure. We flag this gap in the scoping report and note that WhatsApp message history export requires a separate WhatsApp Business API data request.

Moskit mass email campaigns and personalization tokens do not migrate as live campaigns. We deliver a written inventory of every active Moskit campaign with its audience filter, email template, personalization fields, and trigger logic, mapped to Odoo's mail.mass_mailing equivalent. The customer's admin rebuilds campaigns in Odoo using the mail_mass_mailing module (Odoo Marketing Automation app).