Migrate from BrightWork to Trello

BrightWork Projects map directly to Trello Boards. We extract the project name, description, start and end dates, and assigned Project Manager from the SharePoint Project Area list and create one Board per Project. The project manager is set as a Board member with admin role. Portfolio Programs create separate Boards linked via a board reference document rather than a native link, since Trello has no parent-child board hierarchy at the platform level.

BrightWork Programs group multiple Projects and roll up to a portfolio-level Status Report. We map each Program to a parent Board whose purpose is to consolidate related project boards. We deliver a Program-to-Board mapping table as part of the migration output, noting that Trello does not natively roll up status across boards; this requires a Trello Power-Up or manual consolidation process for ongoing use.

BrightWork portfolio-level Status Reports aggregate status across multiple projects into a single executive-readable document. Trello has no native portfolio reporting feature. We extract the latest Status Report data and write it to a reference Card pinned to the parent Program Board, with a written Status Report handoff document that the customer's admin uses to configure Trello Dashboard views (Premium) or a Power-Up for ongoing reporting.

BrightWork Tasks map to Trello Cards with name, description, start date, due date, % complete, priority, assigned owner, and predecessor links preserved. Parent-child task hierarchy migrates as Cards with subtasks represented as Card Checklists, with the parent card labeled 'Parent Task' in the checklist name. Priority maps to Trello Card labels; start and due dates map to Custom Fields of type Date where the Standard or Premium plan is in use.

BrightWork subtasks are represented as Checklist items on the parent Card. Each Checklist item carries the subtask name and completion status. If the Standard or Premium plan is in use, we add a Custom Field of type Checkbox per subtask for individual assignment tracking. Subtasks with their own subtasks are flattened into a single Checklist level, with indentation preserved in the item name text.

BrightWork custom fields are SharePoint list columns with per-project type definitions. We export the column schema for each Project Area and map to Trello Custom Field types: text to Text, numbers to Number, dates to Date, choice columns to Dropdown. Person or Group fields (lookup to SharePoint users) map to a Text Custom Field with the display name. Managed Metadata fields map to Text with the term label. If two Projects define the same custom field name with incompatible types, we surface the conflict for customer resolution before import.

BrightWork Risk entries from the RAID log migrate to Cards on the project Board labeled 'Risk'. Each risk becomes one Card with the risk title, description, owner, impact rating, and status as Custom Fields. High-severity risks receive a red Label. We do not maintain the risk register as a separate list; the labeled Cards serve as the risk record within the Trello board.

BrightWork Issue entries migrate to Cards labeled 'Issue' on the project Board. The Card carries issue title, description, owner, status, and resolution date as Custom Fields. Open issues receive an orange Label. Issues are distinguishable from Risks by label and by the 'Issue Status' Custom Field value.

BrightWork Dependency entries migrate to Cards labeled 'Dependency' on the project Board. Each dependency Card includes the dependent-on project or external party, the dependency type, and the target date as Custom Fields. Dependencies are cross-linked to the related project Card via a Card link (attachment or description URL) since Trello does not support cross-board reference fields natively.

BrightWork file attachments stored in SharePoint document libraries are extracted as binary files and re-uploaded to the corresponding Card as Trello Card Attachments. We preserve the original file name and folder structure within the Card description or as a structured checklist for context. File size follows Trello's plan limits (10 MB Free, 250 MB Standard and above). Files exceeding the target plan limit are noted in the attachment manifest for the customer to host externally and link.

BrightWork time entries logged against Tasks are mapped to Trello Cards as a Custom Field of type Number ('Hours Logged') and a Date Custom Field ('Last Logged'). Trello does not have native time tracking; customers needing ongoing time tracking use a Time Tracking Power-Up post-migration. We do not migrate historical time entries as a separate object since Trello has no equivalent to host them.

SharePoint document libraries within a BrightWork Project Area are exported as file sets. We attach each file to the corresponding Card, grouping files by their original SharePoint folder path within the Card description. For large file sets (over 20 files), we create a summary Card labeled 'Documents' with links to each file, since Cards do not support true folder structures. Customers with extensive document libraries are advised to use a Trello-compatible cloud storage Power-Up post-migration.