Migrate from WORKetc to Odoo CRM

WORKetc Contact records map directly to Odoo CRM Contact. Standard fields (name, email, phone, address) migrate as-is. The contact's lifecycle stage, owner assignment, and any custom field values transfer to equivalent Odoo custom fields. We resolve WORKetc owner references to Odoo User records by email match. Contractor portal users are mapped as Contact records with a custom field contractor_flag set to True rather than as internal User records.

WORKetc Company records map to Odoo CRM Partner records with the company_type field set to company. Company → Contact parent-child relationships are preserved via the parent_id field on Contact. Company-level custom fields migrate to Partner custom fields in Odoo. Company status (active/inactive) maps to Odoo's active boolean.

WORKetc Leads map to Odoo CRM Lead (crm.lead). The lead's status, source, and converted-flagged records migrate with the original conversion date preserved. Leads that were converted to Contacts in WORKetc retain the converted_contact_id and converted_company_id references. We export the full lead lifecycle including status transitions to preserve historical context in Odoo's lead history log.

WORKetc Deals map to Odoo CRM Opportunity (crm.lead with type = opportunity). Deal stage maps to Odoo Stage, deal amount to Expected Revenue, and probability to the stage probability percentage. The deal-to-company association migrates to the Opportunity's partner_id and partner_name fields. Closed-won and closed-lost reasons from WORKetc custom fields map to Odoo's Lost Reason and Won Reason fields.

WORKetc Projects map to Odoo Project. The key migration challenge is WORKetc's Project Types and Stages weighted progress model: each stage carries a custom percentage weight that does not map directly to Odoo's task-count or hours-based progress. We export the full stage configuration including weights and store the original weighted progress in a custom Odoo field original_weighted_progress__c. Odoo's native progress field is recalculated from task completion post-migration. Milestones map to Odoo Project Milestones.

WORKetc Support Tickets can map to Odoo Helpdesk Tickets (helpdesk.ticket) if the Helpdesk app is installed, or to Project Tasks if the customer prefers a project-centric support model. Ticket status, priority, and conversation threads migrate. Conversations migrate as message records on the Odoo ticket. We scope the destination app during discovery based on the customer's Odoo installation.

WORKetc Invoice records migrate to Odoo Account Invoice. Invoice headers, line items, totals, and payment status transfer. However, payment transaction history and linked bank records are external financial data that require separate reconciliation and are noted as a gap in the migration scope. The customer should verify that Odoo's chart of accounts aligns with their billing taxonomy before invoice migration.

WORKetc custom field definitions and values export across all objects. Field types (dropdown, text, date, numeric) are mapped to equivalent Odoo field types: selection fields for dropdowns, char/text for text, date/datetime for dates, float/integer for numeric. Multi-select custom fields in WORKetc map to Odoo char fields storing comma-separated values or to many2many tags depending on Odoo's module configuration. We flag any field type that requires a custom Odoo module to store equivalent data.

WORKetc User records map to Odoo User by email match. We export the full user list including name, email, and role. Permission levels are not directly transferable because Odoo's access control model (ir.model.access) is role-based at the app and record level rather than tier-based like WORKetc. We map WORKetc admin users to Odoo internal users and read-only users to Odoo portal users where applicable.

WORKetc file metadata and record-linked document URLs are exported as attachment references. Actual file binary export depends on Odoo's document storage capabilities (local filesystem, external storage, or an attached external storage app). We export file URLs and names; the customer's admin configures Odoo's document storage before the file migration phase. Files linked to projects and tickets migrate as Odoo attachments on the corresponding records.

WORKetc Knowledge Base articles and category assignments export as article content and category references. Odoo Knowledge (document.page) is a separate app that may or may not be installed in the destination environment. If Odoo Knowledge is not present, we export articles as document records or as text attachments and flag this gap in the scope. Rich formatting and embedded media may require post-migration review for display consistency.

WORKetc web form definitions and field mappings are exported as written specifications. The actual hosted form endpoints are WORKetc-specific and must be replaced with Odoo form endpoints (Odoo Website forms or a third-party form app) post-migration. We deliver a field-level mapping document so the customer's web developer can rebuild the forms with Odoo as the target.