Migrate from KeyedIn to Odoo ERP

KeyedIn Projects map to Odoo Project records. Project name, status (Draft, Active, On Hold, Complete), start and end dates, budget amounts, and owner migrate as direct field mapping. KeyedIn Project custom fields are discovered during scoping and mapped to Odoo custom fields on the project.model.project model. Projects must write before any child Tasks, Resources, or Time Entries to satisfy the parent reference.

KeyedIn Tasks nested under Projects map to Odoo Project Tasks. Parent-child hierarchy is preserved by ordering records by parent reference and writing children after their parent Project is confirmed in Odoo. Start date, end date, assignee (via Resource mapping), and status map to Odoo Task fields. KeyedIn Task custom fields map to project.task custom fields.

KeyedIn Subtasks nested under Tasks map to Odoo Sub-tasks within the parent Task. If the Odoo Project configuration uses only two-level nesting (Project > Task), the lowest-level Subtasks flatten as child Tasks. We confirm the customer's Odoo Project app configuration during discovery and apply the nesting strategy accordingly.

KeyedIn standalone Deliverables at the Project level map to Odoo Milestones. We flag any Deliverable records that also have a corresponding Milestone record inside a linked Task Plan — this dual tracking is KeyedIn's documented structural gap. We present the deduplication list to the customer for resolution and migrate only the resolved canonical records to avoid double-counting project progress in Odoo.

KeyedIn Task Plans are structured schedules attached to Projects containing Tasks, Subtasks, and their own milestone set. We treat Task Plans as Odoo Project Phases, migrating the Phase name and dates. Contained Tasks and Milestones migrate via their respective object mappings. If the customer uses Task Plans as a separate grouping layer, we configure Phases to replicate that grouping in Odoo.

KeyedIn Resources (People or generic pool entities) map to Odoo Employees linked to the Timesheet app. Resource-to-Project assignments migrate as Odoo Timesheet line allocations under the relevant Project. We resolve Resources by email against the Odoo User/Employee table; any Resource without a match enters a reconciliation queue for the customer's admin to provision before Project allocation migration begins.

KeyedIn Portfolios group related Projects for executive visibility. We migrate Portfolio-to-Project associations as Odoo Tags, creating a tag per Portfolio name and applying it to all member Projects. Tags provide a lightweight grouping mechanism in Odoo without requiring a separate Portfolio module. If the customer requires a full Portfolio reporting view, we recommend Odoo Dashboard with tag-based filtering.

KeyedIn Time Entries logged against Tasks or Resources migrate as Odoo Timesheet entries. Each Timesheet line carries the employee (via Resource mapping), project, task, date, hours, and billable flag. We resolve the Odoo Project and Task references before Timesheet migration and set the analytic account on each line for billing integration. Time entries without a resolvable parent Task map to the Project-level Timesheet if Odoo Project app configuration allows.

KeyedIn Enterprise financial data — budgets, cost codes, and period breakdowns stored as separate line items — maps to Odoo Accounting Budget entries under the relevant Analytic Account. Budget amounts must reconcile to the parent Project budget total after migration; we validate this reconciliation and flag any currency mismatches or missing cost codes before write. Odoo Accounting must be installed and configured for this migration plane.

KeyedIn Risks and Issues logged at the Project level map to Odoo Project Issues with severity, status, owner, and description preserved. We link each Issue to its parent Project via the project_id field and preserve the risk categorization as Issue tags. If Odoo has no native Issue module enabled, Issues migrate as Tasks with a custom issue_type = Risk field.

Documents attached to KeyedIn Projects or Tasks are stored with file name, URL reference, and metadata. We migrate file metadata and URLs as Odoo ir.attachment records linked to the parent Project or Task via res_model and res_id. Actual file blobs require a separate file transfer process coordinated with the customer's IT team; we document the required file path mapping as part of the migration runbook.

KeyedIn tenants frequently have custom fields on Projects, Tasks, and other objects with no standard field registry. We perform a full field discovery scan during scoping, enumerate every custom field with its type and object, and generate an explicit mapping to the corresponding Odoo custom field (created via Odoo Studio or metadata). Fields without an Odoo destination are held for customer decision. Skipping this step results in silent data loss on migration.