Migrate your KeyedIn data

Projects are the top-level container in KeyedIn's data model. They carry standard fields for name, status, dates, budget, and owner. We migrate Projects as-is with field-level mapping to the destination schema. Custom properties on Projects are migrated via explicit field mapping identified during discovery.

Tasks are nested under Projects and support parent-child hierarchy, start/end dates, assignees, and status. We preserve the task hierarchy by ordering records by their parent reference and writing them in sequence to maintain the tree structure at the destination.

Subtasks exist as a child level beneath Tasks in KeyedIn. Where the destination does not support a three-level nesting (Project > Task > Subtask), we flatten the lowest level as child tasks under the parent Task and flag the flattening in the mapping document.

Resources in KeyedIn are People or generic pool entities used for allocation and capacity planning. Resource-to-project assignments are migrated as separate allocation records alongside the Project, with a lookup key back to the resource. Named resources require user/person mapping to the destination system.

Portfolios group related Projects for executive-level visibility and reporting. We migrate Portfolio-to-Project associations as a junction object or tag, preserving which projects belong to which portfolio grouping.

KeyedIn uses both Deliverables and Milestones as distinct tracking concepts. Deliverables are standalone milestone records at the project level, while Milestones also exist within Task Plans. This dual tracking is a known source of data duplication. We flag records that exist in both systems and surface them for customer resolution before write.

Task Plans are structured schedules attached to Projects that contain Tasks, subtasks, and their own milestone set. We treat Task Plans as a grouping entity and migrate the contained Tasks and milestones in the correct order. Custom fields on Task Plans are mapped individually.

Time entries are logged against Tasks or Resources and carry hours, dates, and billable flags. We migrate time entries as atomic records with a foreign key to the target Task. If the destination uses a different time entry object, we map the fields by name and validate billable/date/hour constraints.

KeyedIn Enterprise includes financial management with budget tracking per project. Budgets are amounts, cost codes, and period breakdowns stored as separate financial line items. We migrate these as budget objects or cost records in the destination, flagging any currency or cost-code mismatches.

Risks and Issues are logged at the Project level with severity, status, owner, and description. We map these to the destination's equivalent risk/issue object and preserve the link back to the parent Project.

Documents attached to Projects or Tasks are stored with file name, URL reference, and metadata. We migrate the file metadata and URLs where the destination supports document linking; actual file blobs require a separate file transfer step coordinated with the customer.

KeyedIn supports custom fields on Projects, Tasks, and other objects. Custom field schema varies per tenant. We discover all custom fields during the discovery phase, generate explicit mappings for each, and apply them at migration time. Fields without a destination counterpart are flagged and held for customer decision.

KeyedIn uses status values that represent pipeline or workflow stages (e.g. Draft, Active, On Hold, Complete). These are enumerated values, not a separate object. We map status values to the destination's status field and flag any values that do not have a direct equivalent.