Migrate from BrightWork to monday Work Management

BrightWork Projects map directly to monday.com Boards. The project name becomes the board title, project description migrates to the board description field, and start/end dates map to the board's date range column if configured. We create the board in the customer's target Workspace during migration. Projects with no Tasks are created as empty boards with a note indicating no items were found during extraction.

BrightWork Programs group multiple Projects and roll up to portfolio-level Status Reports. We map Programs to a monday.com Board where each child Project becomes a Group on that board, preserving the program-project hierarchy. If the customer prefers flat boards, we link Program-child Project boards using monday.com's Connect Boards integration or item-level links. The Program-level Status Report summary migrates as an Item on the Program board with summary fields.

BrightWork Project Areas are SharePoint subsites containing the project's SharePoint lists (Tasks, RAID, Documents). Where the destination has a single Board per project, we flatten the Area structure into the parent Board. If the customer has configured separate boards for Tasks versus Documents in monday.com, we split the Area content accordingly during transform.

BrightWork Tasks map 1:1 to monday.com Items. Standard fields migrate: task name to item name, start date to Start Date column, due date to Due Date column, % complete to a numeric column (monday.com's native progress column requires Pro plan), priority to Priority label column, assigned owner to Person column. Parent-child task hierarchy maps to monday.com Subitems on Pro plans. Tasks without a parent become top-level Items.

BrightWork custom fields are SharePoint list columns defined per Project Area, not globally. We export each Project Area's column definitions, identify field names appearing across multiple projects, detect type conflicts (e.g., same column name defined as text in one project and number in another), and surface conflicts for customer resolution before import. Compatible custom fields translate to monday.com column types: choice lists to Status or Labels, numbers to Numbers, dates to Date columns, person fields to Person columns. Columns with no monday.com equivalent migrate as text.

BrightWork Risks are structured log entries with fields like Risk Title, Description, Probability, Impact, Mitigation, Owner, and Status. We map Risks to Items on a dedicated monday.com Board (typically named Risks) with columns for Impact (Labels), Probability (Numbers or Labels), Mitigation (Text), Owner (Person), and Status (Status). If the customer uses monday.com's optional Risk Management template, we map to its pre-built columns.

BrightWork Assumptions are structured log entries tracking the assumption statement, category, owner, validation status, and review date. We map Assumptions to Items on a dedicated monday.com Board with text and status columns. Assumptions do not have a native monday.com equivalent and require a configured board structure.

BrightWork Issues are structured log entries with title, description, priority, status, owner, and due date. We map Issues to Items on a dedicated monday.com Board with columns for Priority (Labels), Status (Status), Owner (Person), and Due Date (Date). Issue priority maps to a Labels column with severity values.

BrightWork Dependencies track the dependent item, dependency type (finish-to-start, start-to-start, etc.), target date, and status. We map Dependencies to Items on a dedicated monday.com Board with columns for Dependency Type (Labels), Target Date (Date), Status (Status), and Related Task (Item Link or Text). Complex dependency chains may require manual recreation in monday.com's native dependency column if the Pro plan is licensed.

BrightWork aggregates project status into portfolio-level Status Reports with sections for each project's health, risks, and milestones. We extract the report data as structured JSON and write it to monday.com as a summary Item on the Portfolio board with text columns for each section, or as a document attached to the Portfolio board if the customer prefers PDF preservation. We do not migrate the report's visual layout; the customer rebuilds the report format in monday.com's Dashboard or uses the written data as a starting point.

BrightWork time entries are logged against Tasks with hours, date, user association, and description. monday.com's native time tracking is available on Pro plans and above ($19/seat/mo). We map time entries to monday.com's Time Tracking column on the corresponding Item, or to a separate Time Log board with Items representing each entry if the customer is on Standard. Time entry hours, date, and user association migrate directly; the description maps to a text column.

BrightWork stores file attachments in SharePoint document libraries within each Project Area. We extract the binary files, preserving folder structure, and re-upload them to monday.com attached to the corresponding Board or Item via monday.com's file upload API. Files larger than 500 MB are flagged for chunked upload or alternative delivery. The original file name and any folder path context are preserved in the Item's file description.