Migrate your GUIDEcx data

Projects are the top-level container in GUIDEcx, holding phases, milestones, tasks, and team assignments. We export all project-level fields including custom fields, status, planned end dates, and customer association. Projects created in GUIDE 1.0 and 2.0 are separate objects and must each be scoped independently for migration.

A Phase is a reusable project structure with tasks, assignees, dependencies, and durations. Templates are mapped as Phases. GUIDE 1.0 templates must be cloned to 2.0 via the self-serve tool before we can migrate them as GUIDE 2.0 objects—they do not appear automatically in 2.0. We preserve phase attachments, sort order, and custom field defaults from the template.

Milestones sit above Task Groups in the hierarchy. We export milestone name, planned dates, status, and status_category. Milestones can have dependencies and are often used as project-level checkpoints that cascade to downstream tasks.

Task Groups are a grouping layer below Milestones and above individual Tasks. We export the group name, sort order, assignees, and custom fields. Task Groups carry no separate duration—duration is set on the contained tasks.

Tasks are the core work unit in GUIDEcx. We export task name, instructions, due date, status, status_category, assignees (internal and external), tags, checklist items, subtasks, and dependencies. We flag completed_date and N/A task handling separately because these affect downstream dependency resolution.

GUIDEcx supports Custom Fields V2 with 8 field types (Text, Date, Email, Number, Dropdown, etc.). Custom fields exist at both project level and task level. We preserve field values during migration but note that field definitions must be recreated at the destination because custom field schemas are not always exported in bulk.

Tasks support finish-to-start dependencies by default. We preserve the dependency graph, but we flag known GUIDEcx 2.0 bugs: subtask-child shared dependencies and N/A-marked tasks that break dependency chains. We recompute start dates for blocked tasks based on upstream completion dates during migration.

Tags in GUIDEcx are used for filtering and assigning tasks to owners. We export all tag names and preserve task-to-tag associations. Note that tags on template-level tasks do not always propagate to project-level tasks in GUIDE 2.0—a known bug we flag during scoping.

GUIDEcx distinguishes between internal team members and external customer contacts. Customer Roles must be created in Resource Management before they can be assigned to a project's Customer Team. We export Customer Roles and associated contacts, but role definitions and contact assignments require manual recreation or API-based bulk assignment at the destination.

Checklist items exist on task templates and live tasks. Known issues in the 2026 release notes indicate that checklists on task templates do not reliably show up on project-level tasks, and checklist items can fail to migrate from V1 to V2. We attempt to export checklist data as a structured list field, but recommend post-migration validation.

Attachments can be stored at the project level and at the phase level in GUIDE 2.0. Phases created via API or UI from templates do not carry over attachments—a known GUIDEcx limitation. We export file metadata and URLs where accessible; actual file downloads require separate handling.

GUIDEcx supports time tracking. The GUIDE 2.0 Time Records dataset is documented as missing values for several columns per the 2026 release notes. We export available time record fields but flag that the dataset may have incomplete data and recommend reconciling against live project records post-migration.

Comments on tasks are supported but are not exported via the standard task export. We can retrieve comment threads via the API and represent them as structured note fields in the destination. Embedded media in comments requires separate handling.

GUIDEcx's Report Builder exposes several datasets (Projects, Tasks, Custom Field Details, Time Records). Some datasets have documented bugs in the 2026 release notes—completed_date in Tasks and Cash Value in Projects. We cross-reference report exports with direct API exports to fill known dataset gaps.