Migrate from Project Central to Trello

Each Project Central Project becomes a Trello Board. We extract the Project name, description, status, and custom fields and create a corresponding Board in the destination Trello Workspace. If the source Project contains sub-projects or grouped task sets, we create a Board per top-level Project and configure Lists within that Board to represent task groupings. We do not migrate Project Central Views (which are display configurations) as they have no Trello equivalent; we document the View structure for the customer's PM to replicate as Board Filters and saved Views in Trello.

Project Central Tasks map directly to Trello Cards. We transfer the task name as the Card title, description as the Card description (with SharePoint link references preserved as hyperlinks), due date as the Card due date, and assignee as a Card member. Task hierarchy (parent Tasks with child sub-tasks) maps to Trello Card hierarchy via the Card Hierarchy Power-Up if installed, or as a Checklist on the parent Card with child items listed as checklist entries.

Project Central Task Owners map to Trello Card Members. We resolve each Project Central user by email address against the Trello destination Workspace members. Members who do not yet exist in Trello are flagged for the customer to provision before migration; if the customer uses Atlassian ID matching the same email domain, the accounts auto-link during the Trello invite flow.

Project Central Status workflow values (e.g., To Do, In Progress, In Review, Done) map to Trello Lists on each Board. We configure the Lists during Board setup to match the status values used in the source Project. If the source uses Agile methodology with sprint states, we create Lists that reflect the sprint cadence and document the mapping for the customer's PM to adjust post-migration.

Project Central Tags map to Trello Labels on each Card. We extract the full tag taxonomy (colors and names) and create corresponding Labels in the destination Board. If tags have color coding in Project Central, we replicate the color assignment on the Trello Label. Labels with no corresponding Card are created as empty labels and can be cleaned up post-migration.

Project Central Custom Fields on Tasks require Trello's Custom Fields Power-Up (free). We install the Power-Up on each destination Board during setup and create custom field definitions matching the source type: text fields map to Text custom fields, numeric fields map to Number custom fields, date fields map to Date custom fields, and dropdown-style fields map to Dropdown custom fields. We then populate the custom field values on each Card during the card migration phase.

Project Central stores no native file attachments; only SharePoint links back to documents. We extract the SharePoint URLs from each Task and map them to Trello Card link attachments. If the destination Trello Workspace has the SharePoint Power-Up installed, we configure the SharePoint site connection so that links open directly within Trello. We do not download or re-upload the underlying SharePoint documents; the links are preserved as references.

Project Central supports parent-child task relationships where a parent Task contains sub-Tasks. We map this to Trello in one of two ways depending on customer preference during scoping: as a Checklist on the parent Card with each child listed as a checklist item (no Power-Up required), or as Card hierarchy using the Card Hierarchy Power-Up (free) which renders sub-Cards visually indented under the parent Card. The customer chooses the approach before migration begins.

Project Central activity logs and comments on Tasks map to Trello Card Comments. We extract comment text, author (by email resolution to Trello member), and timestamp. Comments are inserted in chronological order on the destination Card using the Trello API. If Project Central stores internal-only notes separately from comments, we map internal notes to a prefixed Card Comment with a [Internal Note] label.

Task due dates from Project Central transfer directly to Card due dates in Trello. We preserve the original date and time if present; if only a date is stored, we set the Card due time to end of day. If the source includes a due-time component, we include it. Cards without due dates are created with no due date set.

If Project Central supports checklist items on Tasks, each checklist maps to a Trello Checklist on the corresponding Card. Checklist item text, completion status, and ordering transfer directly. Incomplete items appear at the top of the Trello Checklist in their original order.

Project Central Status Workflows are process configurations that define the allowed status transitions per Project. These do not have a direct Trello equivalent as code. We document each Workflow's status values, transition rules, and configured notifications as part of the workflow inventory deliverable. The customer's project manager uses this inventory to configure Trello Lists and, if needed, Butler automation rules to replicate the workflow logic.