Migrate from Genius Project to Trello

Each GP Project maps to a dedicated Trello Board. We preserve the project name as the board name and the project description as the board description. Projects spanning multiple portfolios can be distributed across multiple boards within a single Trello workspace or split across workspaces per customer preference during scoping. Board visibility settings (private, workspace, public) map from GP project visibility if that field is populated.

GP Tasks map to Trello Cards. Task name becomes card title; task description migrates as card description in markdown-compatible format. Start date, due date, and assignee migrate to card metadata. Status in GP (not started, in progress, completed) maps to list membership in Trello. Task priority becomes a Trello label with color coding if GP priority values are configured.

GP Subtasks attached to a parent Task map to checklist items on the corresponding Trello Card. Each subtask's name becomes a checklist entry. Subtask status (checked/unchecked) carries over to checklist item completion state. Subtask assignees do not map to individual checklist member assignments since Trello checklist items are not individually assignable; we note the parent card assignee as responsible for the full checklist.

GP Resources (people, equipment, roles) flatten into Trello workspace members and card member assignments. Each unique GP Resource user with assignments maps to a Trello workspace member added by email. GP resource assignments on tasks transfer as card member assignments in Trello. Capacity percentage, utilization metrics, and role type store as custom text fields on cards or in the card description when the Trello plan does not support custom fields. Equipment and non-person resources map to card description text only since Trello has no equipment resource object.

GP Portfolios group multiple Projects for enterprise-level reporting and governance. Trello has no native portfolio or program object. We give customers two options during scoping: either create one Trello Workspace per portfolio with all portfolio projects as boards within it, or use a consistent board-label prefix (e.g., PORTFOLIO-ABC) to group boards across workspaces. Portfolio hierarchy (parent portfolio, child portfolio) cannot be natively replicated in Trello. Portfolio health summaries and CapEx roll-up data do not have a destination equivalent and are delivered as a written summary document for the customer's records.

GP Stage-Gate stage names and stage order per project map to Trello list names and list position on the destination board. If a GP project has multiple stages defined, we create one list per stage in order on the board. The governance workflow logic (approval gates, conditional routing) does not carry over; we document the stage sequence and gate conditions as a written governance map for the customer to rebuild using Trello Butler or a third-party automation tool. Stage labels and stage metadata migrate as card labels where applicable.

GP Cost Plans store budget line items with category, planned cost, actual cost, and variance per project. Trello has no native budget or financial tracking object. We migrate the total planned budget amount and total actual cost as custom number fields on the project Board or as custom fields on milestone cards if the Trello plan supports them. Cost plan line-item detail (individual category breakdown) cannot be replicated in Trello and is delivered as a structured CSV export alongside the migration. Customers should validate that their Trello plan supports the custom field types (number, currency label) required for their cost categories.

GP CapEx investment records track capital expenditure approvals and amounts at the portfolio or project level. These migrate as custom number fields on the Trello Board or as custom fields on a designated CapEx tracking card. Approval status, approval date, and investment category cannot be natively tracked in Trello; we document these as card description text or as a separate written CapEx summary. CapEx tracking against project milestones requires manual setup post-migration using Butler or a third-party integration.

Documents attached to GP Projects or Tasks migrate as file attachments on the corresponding Trello Cards. We preserve the original filename, file type, and upload date as attachment metadata. Trello attachment size limits (10 MB on free, 250 MB on Standard and Premium via Butler) may require customers to use cloud storage links (Google Drive, Dropbox, OneDrive) for large files. We redirect GP file URLs to a temporary storage location during migration and document the redirect chain for the customer's records. Documents linked to multiple GP projects are attached to each corresponding Trello Card.

GP Users and Owners map to Trello workspace members by email address lookup. Each GP user with active project assignments is added to the Trello workspace and assigned as a card member on tasks where they held an assignment in GP. Inactive GP users are added as workspace guests if their historical assignments need to be preserved on cards; otherwise they are documented in the user mapping inventory. GP role-based access control (admin, project manager, resource) does not map directly to Trello workspace permission roles (admin, normal, guest) and is reconciled during scoping.

GP custom fields extend Projects, Tasks, and Resources with organization-specific data. Trello Standard ($5/user/month) and Premium ($10/user/month) support custom fields including text, number, date, checkbox, and single-select. We discover all GP custom field definitions during scoping, then map each field to the equivalent Trello custom field type. Custom fields on GP tasks map to Trello Card custom fields; custom fields on GP projects map to Board-level custom fields if available. GP custom fields on the free Trello plan migrate as card description text with a labeled prefix (e.g., [CUSTOM FIELD NAME]: value). We confirm the customer's Trello plan during discovery before setting field mapping strategy.

GP stores time entries per task with hours logged, date, and user. Trello does not have a native time-tracking object, though card aging and time-based Power-Ups exist. We migrate time log summaries as structured text in the card description (e.g., 'Time logged: 4.5h on 2025-03-15 by John Smith') preserving the total hours per task. Time log detail for reporting purposes is delivered as a structured CSV alongside the migration. If the customer requires native time tracking post-migration, we recommend enabling a time-tracking Power-Up or integrating with a dedicated time-tracking tool.