Migrate from KeyedIn to Infor CloudSuite Corporate

KeyedIn Projects map to Infor CloudSuite Industrial Work Orders or Project Management entities depending on the CloudSuite edition and configuration. Project name, status, start and end dates, owner, and budget amounts migrate as top-level fields. We use Infor's Project Master or Work Order header as the destination record and preserve the KeyedIn project code as a custom identifier field. If the destination uses Work Orders, the Project maps to the Work Order header with Project Code populated from KeyedIn.

KeyedIn Tasks nested under Projects map to Infor Operations (in the routing context) or Tasks (in the project management context). Parent-child hierarchy is preserved by ordering records by their KeyedIn parent reference and writing Operations in sequence order. Task status, dates, assignee (resolved via Resource-to-Employee lookup), and description migrate directly. If the destination uses standard tasks rather than operations routing, we flatten the nesting to a flat task list under the parent Project or Work Order.

KeyedIn Subtasks under Tasks represent a three-level nesting (Project > Task > Subtask). Infor CloudSuite Industrial typically supports two-level nesting (Project > Operation). We flatten Subtasks as child Operations or tasks under the parent Task, with an operation sequence number assigned to preserve the work breakdown order. If the destination's edition limits nesting depth, the customer chooses between flattening or maintaining a flat task list during scoping.

KeyedIn Resources (People or generic pool entities) map to Infor CloudSuite Employee records or Work Center assignments. Resource-to-project allocations migrate as separate allocation records linked to the Project or Work Order. We resolve KeyedIn resource assignments against the Infor Employee or Work Center table by name or code match during migration. Any KeyedIn Resource without a matching Infor Employee is flagged for the customer to provision before the allocation records are written.

KeyedIn Portfolios group related Projects for executive visibility. We migrate Portfolio-to-Project associations as a custom tag or classification field on the Infor Work Order or Project record, or as a Project Group entity if the destination CloudSuite edition exposes it. The customer chooses the target strategy during scoping. Portfolio metadata (name, description, owner) migrates as a separate reference record.

KeyedIn standalone Deliverables map to Infor CloudSuite Work Order Milestones or Project Milestones depending on the configuration. We flag any Deliverable that also has a corresponding Milestone in an attached Task Plan (duplicate representation of the same milestone) and present these to the customer for resolution before migration. Only the resolved canonical Deliverable record migrates to avoid double-counting in progress reporting. We preserve the original KeyedIn Deliverable ID in a custom field for audit trail.

KeyedIn Task Plans contain Tasks, Subtasks, and their own embedded Milestones. We treat the Task Plan as a grouping entity and migrate its contained Tasks and Milestones against the parent Project or Work Order. Milestones embedded within the Task Plan that duplicate standalone Deliverables are flagged during the Deliverable resolution phase. Task Plan-level scheduling constraints migrate as project scheduling fields in Infor.

KeyedIn Time Entries logged against Tasks or Resources map to Infor CloudSuite Time Transactions or Labor Postings. Hours, dates, billable flags, and cost codes migrate as labor transactions linked to the Work Order Operation or Project Task. If Infor uses Shop Floor Control, time entries route through the MES time collection interface; we map KeyedIn hours to the appropriate Infor time transaction type. We preserve the original KeyedIn time entry ID for reconciliation.

KeyedIn Enterprise financial budgets (amounts, cost codes, period breakdowns) migrate as Infor Budget records or cost code assignments on the Work Order. Budget amounts and cost codes map to Infor cost object structures. We treat financial data as a separate migration plane from tasks and validate that migrated budget totals reconcile to the parent Project budget in Infor. Any currency mismatches or missing cost codes are flagged before write. Period breakdown migrates as budget distribution records against the Infor fiscal calendar.

KeyedIn Risks and Issues logged at the Project level map to Infor CloudSuite Project Risk or Issue records with severity, status, owner, and description. We preserve the link back to the parent Project or Work Order via the Infor lookup field. If the destination CloudSuite edition does not expose a native risk object, we migrate these as Project Notes or custom fields with a type discriminator.

Documents attached to KeyedIn Projects or Tasks (file name, URL reference, metadata) migrate as Infor Document Management records or ContentLink attachments. We migrate file metadata and URL references; actual file blobs require the customer to migrate the document repository separately or use Infor's Document Management to re-link existing files. We document the original file locations for the customer's IT team to handle the blob migration.

KeyedIn tenant-specific custom fields on Projects, Tasks, and other objects are discovered during the scoping scan and mapped to Infor CloudSuite custom fields by type (text, number, date, picklist). Infor's Custom Field Mappings tab (ION BOD mapping) handles the field-level mapping for integration-sourced data; we apply the same field-level mapping during migration database load. Any KeyedIn custom field without an Infor destination is flagged for the customer to decide whether to create a new field or drop the data.