Migrate from PromoXcrm to Odoo CRM

PromoXcrm Lead records with customizable pipeline stage names (e.g., Quote Sent, Artwork Approved, Order Confirmed) map to Odoo crm.lead records. Stage names migrate as custom stage values on the crm.lead.stage model using a mapping table built during scoping. Lead source, owner email, and any promo-specific lead custom fields transfer to corresponding char, many2one, or selection fields on crm.lead.

PromoXcrm Client records map to Odoo res.partner. Standard fields (name, email, phone, company) migrate directly. PromoXcrm's client-facing contact types (end customer vs distributor) map to res.partner partner_latitude/longitude custom fields or tags. Any promo-specific custom properties on the Client record require pre-creation in Odoo Studio before import.

PromoXcrm's customizable pipelines with stage names tailored to promo workflows become Odoo crm.lead.stage records. We create one stage sequence per PromoXcrm pipeline during Odoo configuration. Pipeline-to-pipeline mapping is preserved as a custom selection field pipeline_name__c on crm.lead so that multi-pipeline data separates cleanly in Odoo's Kanban view.

PromoXcrm Projects representing individual promo orders or campaigns map to Odoo project.project records linked to crm.lead via a many2one relationship. Project dates, status, associated contacts, and order details transfer to custom fields on project.project. If the PromoXcrm Project has a deal-like financial value, we also create a corresponding crm.lead with the projected revenue and link it to the project.task records for pipeline reporting.

PromoXcrm Task records with assignees, due dates, and status map to Odoo project.task. Task-to-project linkage transfers as project_id. Automated task-creation rules from PromoXcrm (if-this-then-that logic) do not migrate; we document all active automations during discovery and provide an Odoo Server Action equivalent for each to be rebuilt by the customer's admin.

PromoXcrm Commission Records track rep or distributor commissions on individual promo orders and have no standard Odoo equivalent. We export these as structured CSV and map commission amount, rate, and associated rep to custom float fields commission_amount__c and commission_rate__c on crm.lead, plus a many2one to res.partner (the rep). The customer's admin creates these fields in Odoo Studio before import; commission recalculation logic requires a separate Odoo product.pricelist configuration post-migration.

PromoXcrm Presentations are internal or client-facing sales assets stored within the CRM. We export available file references (file names, URLs, metadata) from PromoXcrm and re-link them post-migration as ir.attachment records attached to the corresponding crm.lead or project.task via res_id/res_model. Actual file hosting transfer depends on PromoXcrm's export capabilities; if direct file export is unavailable, we document the file list so the customer's admin can re-upload to Odoo's document management or Portal.

PromoXcrm's accessible custom objects (confirmed via web-service API) map to Odoo custom models created via Settings > Technical > Database Structure > Models. We pre-create the destination schema including all custom fields, field types, and any lookup relationships to crm.lead or res.partner during the Odoo configuration phase. Custom object naming follows Odoo's model convention (x_customobjectname without spaces). Data migrates via Odoo's data import CSV with the custom model as target.

PromoXcrm Owners referenced on Lead, Client, Project, and Task records map to Odoo res.users by email match. Owners without a matching Odoo User go to a reconciliation queue for the customer's admin to provision before record import resumes. If PromoXcrm Owner records include role or territory data, we store this in a custom char field owner_role__c on crm.lead.

PromoXcrm's product catalog items used in quoting map to Odoo product.product records. Product name, SKU (product_code), and list price transfer directly. If PromoXcrm stores supplier information for promo items, this maps to Odoo's seller_ids on product.product. Product categories map to product.category.

PromoXcrm internal notes on Leads, Clients, or Projects map to Odoo mail.message records linked to the corresponding crm.lead or res.partner via res_id and model. Note body migrates as HTML content with any file attachments transferred as mail.message.attachment records.

PromoXcrm manually created task engagements (distinct from automated task rules) map to Odoo project.task with Stage, assignees (user_ids), and date_deadline preserved. Activity timeline ordering is preserved by setting create_date to the original PromoXcrm timestamp.

PromoXcrm integrations with Xero, Stripe, and Mailchimp are native connection configurations that do not export. We document which integrations were active during discovery so the customer's admin can configure equivalent Odoo native modules (account_xero, payment_stripe, mass_mailing_mailchimp) or third-party connectors from the Odoo Apps afterward.