Migrate from KeyedIn to Epicor Prophet 21

KeyedIn Projects map directly to Epicor Kinetic Projects. The Project Name, Status, Start Date, End Date, and Owner migrate as-is. Budget amounts from KeyedIn map to Epicor's Project Budget (Phase Budgets or direct Cost Category amounts). We validate total budget reconciliation after import because KeyedIn financial data may exist in a separate data plane from project task data.

KeyedIn Task Plans are standalone schedule entities attached to Projects. Epicor Kinetic has no separate Task Plan object; tasks live as WBS Phases within a Project. We map each KeyedIn Task Plan to the parent Project and its Tasks to WBS Phases. The Task Plan name is preserved as a Project Phase or WBS Group label. Epicor WBS supports two hierarchy levels (Project > Phase > WBS Task), so deeply nested Task Plans may require flattening at the lowest level.

KeyedIn Tasks nested under Task Plans map to Epicor WBS Phases or WBS Tasks. Parent-child hierarchy is preserved by ordering records by parent reference and resolving the parent WBS Phase ID at migration time. Start/end dates, assignees, status, and percent complete migrate directly. Epicor's WBS does not support a three-level nesting equivalent to Project > Task Plan > Task > Subtask; we flatten Subtasks as child WBS Tasks under the parent Task Phase.

KeyedIn Subtasks nested under Tasks are mapped to Epicor WBS Tasks as the lowest hierarchy level. Epicor WBS Phase and WBS Task objects share the same Erp.BO.Project and Erp.BO.WbsSvc APIs, and WBS Tasks under a WBS Phase are the natural landing point for subtask records. The parent Task must be migrated first so that the WBS Phase reference is available when writing Subtask records.

KeyedIn Resources (People or generic pool entities) map to Epicor Kinetic Employee records. Resource-to-project assignments migrate as Labor entries with allocation hours, date, and billable flag. We resolve the Employee record by matching the KeyedIn resource email or name to the Epicor Kinetic employee table. If the Employee does not exist, we hold the record in a reconciliation queue for the customer's admin to provision the employee before labor allocation migration proceeds.

KeyedIn Portfolios group related Projects for executive visibility. Epicor Kinetic does not have a native Portfolio object; we map Portfolio-to-Project associations to Epicor's Project Group feature or attach a custom Project Tag field to each Project record. The customer chooses the grouping strategy during scoping. Multiple KeyedIn Portfolios that reference the same Project are preserved as separate Project Group memberships.

KeyedIn standalone Deliverables are milestone records at the project level. Epicor Kinetic does not have an equivalent standalone Deliverable object. We map Deliverables to WBS Phase Milestone attributes where the destination WBS Phase structure supports milestone flags, or to Project Issue records with a milestone-type classification for cases where Epicor's Issue/Risk tracking is used for milestone governance. If the same milestone exists as a Task Plan Milestone, we flag it as a duplicate for customer resolution before migration.

KeyedIn Milestones embedded within Task Plans map to Epicor WBS Phase Milestone attributes. The milestone name, due date, and status migrate as Phase milestone fields. We validate that the parent Task Plan (mapped to WBS Phase) exists before writing the milestone. Deliverables that represent the same milestone are flagged for deduplication against Task Plan Milestones.

KeyedIn Time Entries logged against Tasks or Resources migrate to Epicor Kinetic Labor transactions (Erp.BO.LaborSvc). Hours, date, labor type, and billable flag map directly. The Labor Transaction is linked to the resolved WBS Phase (from the KeyedIn Task) and Employee (from the KeyedIn Resource). If the destination uses project-specific labor entry approval workflows, we flag these for configuration after migration.

KeyedIn Enterprise financial budgets (amounts, cost codes, period breakdowns) migrate to Epicor Kinetic Project Budgets and Cost Categories. We treat financial data as a separate migration plane from task data because KeyedIn stores budgets not always co-located with Project and Task records. Budget amounts are reconciled to the parent Project total after migration. Currency mismatches or missing cost codes are flagged before write.

KeyedIn Risks logged at the Project level with severity, status, owner, and description map to Epicor Kinetic Project Risk records. We preserve the link to the parent Project and validate that the Project record exists in Epicor before writing the Risk. Epicor Kinetic uses the Erp.BO.RiskAndIssueSvc for Risk and Issue records.

KeyedIn Issues logged at the Project level map to Epicor Kinetic Project Issue records via Erp.BO.RiskAndIssueSvc. Status, priority, owner, description, and related Project are migrated directly. Issues that reference a KeyedIn Task Plan or Task are linked to the corresponding WBS Phase after hierarchy migration completes.

Documents attached to KeyedIn Projects or Tasks are stored with file name, URL reference, and metadata. We migrate file metadata and URLs as Epicor DocStar attachments or as URL-type links on the Project record. Actual file blob migration depends on the Epicor edition's document management configuration. We flag the document storage approach during scoping.

KeyedIn custom fields on Projects, Tasks, and other objects are tenant-specific with no standard field registry. We perform a full field discovery scan during scoping to enumerate every custom field, map each to an Epicor Kinetic UD Column definition, and deploy UD fields before record migration. Complex custom fields that require BPM logic (such as cascading values or cross-object derivations) are flagged for post-migration Epicor developer configuration.