Migrate from edge CRM to Odoo CRM

edge CRM Contacts map to Odoo res.partner records with partner_type set to contact. First name and last name from edge CRM map to firstname and lastname on res.partner using the base_name_autocomplete module conventions. Email, phone, and mobile map to email, phone, and mobile. Custom contact properties on edge CRM require pre-creation in Odoo Studio as custom fields on res.partner before import; we document each field's edge CRM data type and the closest matching Odoo field type to avoid truncation or type-rejection errors.

edge CRM Companies map to Odoo res.partner records with partner_type set to company. Company name maps to name, domain or website maps to website, and address fields map to street, street2, city, state_id, zip, and country_id. The company record must exist before any linked Contacts import so that the parent_id foreign key resolves on insert. edge CRM's company-contact association table is preserved as parent_id references in Odoo.

edge CRM Leads map to Odoo crm.lead records with type set to lead. The AI qualification score from edge CRM transfers to a custom field x_edge_lead_score__c that we create in Odoo Studio before import. Lead status maps to crm.lead stage_id with stage names remapped from edge CRM's stage labels to the nearest Odoo crm.stage values. edge CRM's lead-company association (linked Company on the Lead record) maps to partner_id on crm.lead.

edge CRM Deals map to Odoo crm.lead records with type set to opportunity. Deal name maps to name, monetary value maps to planned_revenue, expected close date maps to date_deadline, and deal owner maps to user_id resolved via email match against Odoo res.users. The edge CRM pipeline stage assignment maps to stage_id, and the associated Company and Contact links map to partner_id and the partner_id contact. Closed-won and closed-lost outcomes from edge CRM map to Odoo's crm.lead won and lost stage states.

edge CRM allows custom stage names and sequence ordering per pipeline. We extract the full stage list including custom names and positions, then configure corresponding crm.stage records in Odoo CRM's kanban view. Each stage is assigned the correct sequence number and probability percentage matching the edge CRM configuration. If the customer has multiple pipelines in edge CRM, we create separate Sales Teams in Odoo and configure stage sequences per team.

edge CRM allows teams to define custom properties on Contacts, Companies, Deals, and Leads. We extract the full custom field schema during the audit phase, then pre-create each field in Odoo Studio on the corresponding model (res.partner or crm.lead) before data import. We flag fields where the edge CRM data type (multi-select, long-text, date) has no direct Odoo equivalent and document the transformation approach. Multi-select picklist values from edge CRM are stored as comma-separated strings in the Odoo custom field unless the customer requests a dedicated ir.model.selection setup.

edge CRM activity logs (calls, emails, meetings, notes) map to Odoo mail.message records linked to the corresponding crm.lead (opportunity or lead) or res.partner record via model, res_id, and message_type fields. Call duration, disposition, and recording reference transfer to custom message fields on mail.message. Meeting location and attendee information map to mail.message body fields. The original edge CRM timestamp is preserved as mail.message.date so the Odoo chatter timeline is chronologically accurate from day one of cutover.

edge CRM tasks with due dates and assignment map to Odoo project.task if the customer activates the Project module alongside CRM, or to internal follower tasks on crm.lead if Project is not in scope. Completed and open tasks both transfer; overdue status from edge CRM is stored as a date field in the Odoo destination task rather than a system flag. Task assignments resolve by email match to Odoo res.users.

Documents stored in edge CRM's document management module can be exported as binary files if the edge CRM export mechanism exposes a download endpoint or a support-assisted bulk export. We flag attachments during scoping, assess per-record whether a download is available, and import files as IR.attachment records in Odoo linked to the corresponding res.partner or crm.lead via res_model and res_id. If edge CRM does not expose file downloads, we document the attachment inventory for manual re-upload post-migration.

edge CRM record owners map to Odoo res.users by email address match. We extract the distinct owner list from all migrating record types and resolve each against the destination Odoo instance's user table. Any edge CRM owner without a matching Odoo user is placed in a reconciliation queue for the customer's Odoo admin to provision before the record import phase begins. Inactive Odoo users are used for historical owner assignment if the original edge CRM owner is no longer active.

edge CRM's built-in Smart PDF Builder generates proposals and invoices attached to Deals. If the customer has activated the Odoo Sale or Accounting modules, these documents map to sale.order (quotations and sales orders) or account.move (invoices). The Odoo document type is confirmed during scoping, and if neither Sale nor Accounting module is in the destination Odoo configuration, we document the proposal content for manual re-creation and flag it as out-of-scope.

edge CRM tags on Leads and Deals map to Odoo crm.tag records. We extract all distinct tag values, create the corresponding tags in Odoo, and link them to crm.lead records via the crm.tag.rel many-to-many table during import. Tag names are preserved verbatim so reporting by tag in Odoo matches the edge CRM segmentation the team is already familiar with.

edge CRM links Leads to Companies through a separate association table. In Odoo, this maps to the partner_id field on crm.lead where the Company is a res.partner record of company type. We resolve the Company reference at migration time using the Company name or domain as the dedupe key against Odoo's existing res.partner records, then populate partner_id on the related crm.lead so the lead-company association is intact in the Odoo chatter view.

Dashboard configurations, saved reports, and chart layouts built inside edge CRM's reporting module are not exposed via a portable export format and cannot be migrated. We document the full list of edge CRM reports with their dimensions, filters, and chart types as a written handoff to the customer's Odoo admin for rebuild using Odoo's reporting tools (native graph views, custom reports, or FoxERP reporting extensions). This is explicitly out-of-scope for the migration deliverable.