Migrate from YetiForce CRM to Odoo CRM

YetiForce Organization records map directly to Odoo CRM Account records. Organization name becomes Account name, address fields map to street, street2, city, state_id, zip, and country_id, and industry type maps to Odoo's industry_id field via a value translation table. Account is created first in migration order to satisfy the parent-record lookup that Contacts and Opportunities require. The YetiForce assigned_user_id is resolved to an Odoo User record by email matching.

YetiForce Contact records map to Odoo CRM Contact records with name, email, phone, mobile, and address fields transferred directly. The parent_organization_id on the Contact resolves to the migrated Account record by organization name match. We preserve the contact's title (Salutation), function, and any custom fields from YetiForce via the dynamic field schema map built during the audit phase.

YetiForce Lead records map to Odoo CRM Lead (crm.lead) records. Lead source and lead status custom fields from YetiForce map to Odoo's source_id and stage_id fields. Any YetiForce lead scoring or rating values are preserved as custom float or integer fields on the Odoo Lead record. Unconverted Leads remain as Leads in Odoo; Leads that represent pre-conversion prospects map to crm.lead with lead_type = lead rather than opportunity.

YetiForce Potentials are the pipeline deal object and map to Odoo CRM Opportunity records. The potentialname field maps to Opportunity name, related_organization_id resolves to the migrated Account, amount maps to Odoo expected_revenue, and the YetiForce sales_stage maps to Odoo stage_id via a configuration table that the customer reviews and approves during scoping. Probability is either inherited from the stage configuration or preserved as a custom field if YetiForce held a manual probability value.

YetiForce potential sales stages (Mapped, Proposal, Negotiation, Closed Won, Closed Lost, etc.) map to Odoo CRM stage records within the appropriate pipeline. We create each Odoo stage with the matching name and configure probability percentages from YetiForce's stage probability values. If YetiForce used custom stage names, we build a translation table during scoping so the customer confirms the Odoo stage mapping before migration begins.

YetiForce Project records map to Odoo Project.project records with name, description, start date, end date, and assigned user preserved. The project status (In Progress, Completed, On Hold, Cancelled) translates to Odoo project state via a value mapping table. Custom fields on YetiForce Projects use tree picklists and reference field types that require type-aware mapping; we handle these via the dynamic schema map and flag any fields that require Odoo custom field creation before import.

YetiForce Project Task records map to Odoo Project.task records linked to the migrated Project by project name matching. Task subject becomes task name, status maps via a stage translation table, priority maps to priority, and assigned_user resolves to the Odoo User by email. Parent task hierarchies from YetiForce are preserved as parent_id references in Odoo, resolving the parent task record by subject name within the same project.

YetiForce Ticket records map to Odoo Helpdesk Ticket (helpdesk.ticket) records if the destination Odoo instance has the Helpdesk app installed. Ticket title, description, status, priority, and category transfer directly. Related Contact and Organization references from YetiForce resolve to migrated Odoo Contact and Account records. If Helpdesk is not installed, Tickets map to crm.lead records with a custom ticket reference field and ticket_category as a tag.

YetiForce Product records map to Odoo Product.product records with name, default_code (SKU), list_price, standard_price, description, and vendor link preserved. The vendor reference from YetiForce resolves to the migrated vendor Contact by vendor name matching. If the Odoo instance has the Inventory app enabled, product type (stockable, consumable, service) maps from YetiForce's product type field.

YetiForce Service records share the same data shape as Products and map to Odoo Product.product records with type = service. Price per unit and description transfer directly. The migration is straightforward provided the Odoo instance has the Service feature enabled in the Product form configuration. If the customer uses Odoo subscription management, recurring plan fields are left as custom fields for the admin to configure post-migration.

YetiForce Vendor records map to Odoo CRM Contact records with the vendor flag set to True. Vendor name becomes Contact name, website maps to website, and address fields transfer directly. We resolve the vendor reference in Product records by matching on vendor name after the Vendor migration phase completes. If the Odoo instance has the Purchase app installed, vendor records can alternatively be created as Purchase.supplier records.

YetiForce User records carry login, name, role, and preference data. Direct user-to-user migration is not supported because Odoo User provisioning is an administrative act requiring password setup and security group assignment. We extract all YetiForce users by email and name and present them as a provisioning list to the customer's Odoo admin before migration begins. Ownership assignments on migrated records then resolve by email match.