Migrate from Knack to Odoo CRM

Knack Tables holding person records (Customers, Contacts, Employees) map to Odoo CRM Contact. The table's text fields map to name, email, phone, street, city, and other standard address fields. We inspect the field inventory per table during discovery and apply Odoo field types (char, text, selection, many2one) based on the Knack field type detected. Email fields are validated for format before insert to avoid Odoo mail.thread constraints.

Knack Tables holding company or organization records map to Odoo Account (commercial partner). Fields mapping includes name (company name), website, and address fields. We create the Account before importing any related Contact so that the Contact's parent_id (commercial_partner_id) relationship is satisfied at insert time.

Knack connection fields linking a person Table to an organization Table are translated into Odoo Contact.parent_id (commercial_partner_id). If the Knack app models multiple contact roles per organization (for example, a company Table linked to a contacts Table with a role field), we split these into separate Contact records with matching parent_id and add a function field or related field to carry the role.

Knack Tables tracking deals, projects, or sales opportunities map to Odoo CrmLead. The Knack pipeline stages map to Odoo stage_id within the relevant crm.team. Probability percentages migrate from Knack custom fields to Odoo's probability field. If the Knack app uses a currency field, we map it to Odoo's expected_revenue with currency_id resolved via res.currency lookup.

Knack pipeline concepts (defined via Table structure and Views) translate to Odoo CrmTeam records with their own stage sequences. Each Odoo stage belongs to a team_id, allowing multi-team pipeline isolation. Stage names and probabilities are created as configuration records before opportunity import.

Knack Tables listing products or services map to Odoo ProductTemplate. Knack fields for name, description, SKU, and price map to product.name, product.description, product.default_code, and product.list_price. Product variants (if modeled as separate Knack records) map to product.product variants under the same template.

If the Knack app includes invoicing or billing records, they map to Odoo AccountMove (invoice and payment records). We flag whether the destination Odoo instance includes the Odoo Invoicing or Accounting module; if not, we document invoice records in a separate accounting migration scope. Journal assignment and fiscal position mapping are applied during import.

Knack Tables holding tasks, to-dos, or action items map to Odoo ProjectTask if the destination includes Odoo Project, or to crm.lead.tasks (mail.activity records) within CRM if no Project module is active. We resolve the assigned user via email match against Odoo res.users and set the stage and priority fields from the corresponding Knack fields.

Knack note records (freeform text entries attached to a Table) map to Odoo mail.message records linked to the parent model (res.partner, crm.lead, etc.) via res_model and res_id. Note body migrates as mail.message.body with message_type = note. Author is set to the Odoo user resolved from the original Knack note creator.

Knack file fields storing documents, images, and PDFs map to Odoo ir_attachment. We download each file from the Knack direct URL (which requires authentication), re-upload to Odoo using the /web/binary/attachment API, and link the attachment record to the correct res_model and res_id. If the destination Odoo instance uses file storage (database or filestore), we configure the appropriate attachment.store_fname during upload.

Knack Views are saved filtered or sorted subsets of a Table and are a Knack UI concept. We document every Knack View during discovery, listing its name, the Table it applies to, and the filter conditions. These are translated into Odoo ir.filters records (saved views) that apply the same filter logic to the corresponding Odoo model. Actual View UI replication is out of scope.

Knack scheduled tasks (available on Pro and above) run background jobs at defined intervals. We flag their existence, document the schedule and action, and deliver a separate inventory of Odoo Automated Actions or Server Actions that the customer's admin should configure to replicate the same schedule. Cron job migration as code is out of scope.