Migrate from Amwork to Odoo CRM

Amwork Contacts map to Odoo res.partner records with partner_type set to 'contact'. We map Amwork's contact name, email, phone, address, and lifecycle stage fields to Odoo's standard res.partner fields, with lifecycle stage preserved as a custom Char or Selection field on the partner record. Owner assignment from Amwork maps to Odoo User via email match. If Amwork contacts are linked to a company, we resolve the Amwork Company record to an Odoo res.partner with partner_type 'company' and set the contact's commercial_partner_id to the company partner.

Amwork Companies map to Odoo res.partner records with partner_type = 'company'. We map company name, domain, industry, and address fields. The company domain from Amwork becomes the Website field on the Odoo partner record. Company records are created before any linked Contacts to satisfy the commercial_partner_id lookup at Contact insert time. Multi-workspace Amwork accounts may map to multiple Odoo company records under separate Odoo company records in a multi-company Odoo configuration.

Amwork Deals map to Odoo crm.lead records. The Amwork deal stage name maps to an Odoo Stage value within the CRM pipeline Kanban. We pre-create Odoo CRM stages matching Amwork stage names before import so that deal values and stage assignments land cleanly. Deal amount, close date, probability, and owner assignment migrate to crm.lead fields: planned_revenue, date_deadline, probability, and user_id respectively. Amwork Deals that are not yet qualified map as crm.lead records awaiting conversion; Deals that represent active opportunities map as Opportunities in Odoo's pipeline view.

Amwork Leads in the separate Leads section map to Odoo crm.lead records with type = 'lead'. Amwork lead status maps to Odoo Stage within the Leads Kanban. We preserve the Amwork lead score as a custom Float field on the Odoo crm.lead. Leads that should convert to Opportunities during migration are flagged in the scoping phase; Odoo's crm_lead2opportunity_partner wizard is used post-migration for leads that convert after cutover.

Amwork Sales Pipelines with customizable stages map to Odoo CRM Teams. Each Amwork pipeline becomes a separate Odoo CRM Team with its own stage sequence. We configure the stage names and probabilities in Odoo CRM's pipeline settings before importing deals, ensuring that deal stage assignments match the Odoo stage ID rather than a stage name string. This prevents orphaned stage assignments if Odoo's stage names change post-migration.

Amwork Projects map to Odoo project.project records. We map project name, description, status, and dates. Project member assignments from Amwork map to Odoo project.member records linked to the corresponding Odoo User. Project templates in Amwork map to Odoo project templates if the Odoo Project app is installed. If Odoo Project is not present in the destination instance, we flag the requirement to the customer during scoping and deliver project records as tagged crm.lead notes.

Amwork Tasks inside Projects map to Odoo project.task records. We map task name, description, assignee, due date, priority, and checklist sub-items (as Odoo subtasks or embedded checklists). Parent-child task hierarchy is preserved via Odoo's parent_id field on project.task. Task-stage mapping (e.g., To Do, In Progress, Done) is created as Odoo project stage values. Tasks linked to a deal or contact in Amwork are cross-referenced in Odoo using a custom Many2one field to crm.lead or res.partner.

Amwork time entries log against Tasks and Projects. We map them to Odoo account.analytic.line (timesheet entries) with the task_id and project_id lookups resolved at migration time. The Amwork time entry duration, date, description, and billable flag map to unit_amount, date, name, and analytic_line_tag respectively. Note that Odoo timesheet entries require an Employee record as the user reference; we resolve the Amwork task owner to an Odoo Employee via email match and create a minimal Employee record if one does not exist. Time entries that were attached to contacts in the source without a project are preserved as read-only notes on the linked Contact.

Amwork custom contact fields require pre-creation of Odoo custom fields on res.partner before migration. We read the Amwork custom field definitions (type: text, number, date, choice), create matching Odoo ir.model.fields records with the correct ttype (char, float, date, selection), and map the custom field values during the Contact import phase. Multi-choice Amwork fields map to Odoo selection fields with explicit key-value pairs.

Amwork custom task fields (activated at the project level) map to Odoo custom fields on project.task. We pre-create the Odoo field definitions using Odoo's ir.model.fields API before task migration, mapping Amwork field types to the nearest Odoo ttype. This mirrors the Amwork project-level activation model. If the Odoo Studio app is available, we use Studio for field creation; otherwise we use direct ORM calls.

Amwork Users referenced on Deals, Contacts, Companies, Tasks, and Projects map to Odoo res.users records. We resolve by email match against the destination Odoo instance's user list. Any Amwork Owner without a matching Odoo User is held in a reconciliation queue; the customer's Odoo admin provisions the missing User before record migration resumes. Active and inactive status is preserved in a custom field on the Odoo user record.

Amwork Workspaces are the top-level organizational unit containing projects, users, and settings. For single-workspace Amwork accounts, we map the workspace to the primary Odoo res.company record. For multi-workspace accounts, we map each Amwork workspace to a separate res.company in Odoo's multi-company configuration, with crm.team records scoped per workspace. This is configured during the schema design phase before any record migration begins.

Amwork file attachments on tasks and deals migrate as Odoo ir.attachment records linked via res_model and res_id to the corresponding project.task or crm.lead record. Large attachment batches are chunked into batches of 100 files to stay within Odoo API throughput limits. Files exceeding Odoo's attachment size limit are preserved as hosted URLs in a custom URL field on the record, with the customer informed of the limit before migration.

Amwork BPMN automation rules and email follow-up sequences are configuration objects and do not migrate. We do not migrate automation rules as code because they are platform-specific and require re-authoring in Odoo. We deliver a written inventory of every active Amwork automation rule with its trigger conditions, actions, and recommended Odoo equivalent (Odoo Studio server action, automated action, or base.automation rule). The customer's Odoo admin or a certified Odoo partner rebuilds them post-migration.