Migrate from Braid to monday Work Management

Braid Projects map to monday.com Boards as the primary container. Project name becomes the Board name, project status maps to a Status column, start and due dates map to Timeline columns if available (Pro and Enterprise), and project description maps to the Board description. Archived projects migrate to an Archived folder in monday.com rather than as active Boards to preserve storage and workspace clarity.

Braid Resources map to monday.com Team Members. We map the resource name, email, role, and capacity settings. Braid's multi-location flag maps to a Location column or a tag set on the Team Member profile. monday.com assigns seat licenses to migrated Team Members based on the destination plan tier (Standard or Pro required for full resource management features). Resources without a monday.com license are created as Guests with limited access if budget constraints apply.

Braid Clients are organizational entities owning engagements. We migrate them as either a dedicated Client board (one board per client with project sub-items) or as Groups within a master Client Relations board, depending on the customer's preference stated during scoping. Client name, contact email, and billing details map to text and email columns. The linked Project set is preserved as board or group references.

Braid Time Entries (hours, dates, billable flags, associated Resource and Project) map to monday.com Items on the relevant Project board. A Hours column (number), Date column (for the entry date), and a Status or Label column (for billable/non-billable flag) capture the core entry data. We aggregate hours by Resource and Project using monday.com Formula columns. Approval status from Braid is stored as a Status column value for admin review post-migration.

Braid budget-versus-actual figures per project do not have a native monday.com equivalent. We map budget amounts to a Number column (Budget), actual amounts to a Number column (Actual), and create a Formula column calculating Variance as Actual minus Budget. The customer configures currency formatting and any conditional formatting rules in monday.com post-migration because monday.com lacks a native accounting module. Revenue recognition settings from Braid are preserved as a text field for reference; the customer maps these to their billing system's settings.

Braid custom fields scoped to Projects or Resources require a pre-migration discovery pass to enumerate all field names, types, and picklist values. We map field types to their monday.com equivalents: text fields to Text columns, numbers to Number columns, dates to Date columns, and picklists to Dropdown or Label columns. Any unsupported field types (for example, multi-currency fields requiring accounting precision) are flagged as text with a note for the customer's admin to reclassify post-migration.

Braid employee schedules map to monday.com Timeline columns on the Project board (Pro and Enterprise feature). Soft-booking versus firm-booking distinctions are preserved as a Label column with values indicating booking type. Availability and allocation data from Braid are stored as number columns on the Resource board for reference, but monday.com's capacity view requires the customer to configure the resource management dashboard post-migration.

Braid multi-location tags on Resources and Projects map to monday.com Location columns if the destination plan includes the Location feature (Pro and Enterprise), or as text Tags on Standard. We preserve location names and allow the destination workspace to filter or group by geography. Location data from Braid that includes timezone information maps to a Text column for reference.

Braid engagement records (calls, meetings, notes attached to projects) map to monday.com Item Updates as a chronological activity log, or as Subitems on the relevant item if the structure is hierarchical. We preserve the engagement type, date, and description. monday.com does not have a native Activity timeline equivalent to a CRM, so engagement history is surfaced as a structured update log rather than a timeline object.

Braid permission sets scoped to Resources map to monday.com workspace and board permission levels. Admin users from Braid map to monday.com Workspace Admins; regular Resources map to Members or Editors depending on their Braid role. We flag any Braid permission scopes that have no direct monday.com equivalent (for example, project-level versus workspace-level access granularity) and document the closest monday.com permission setting for the customer's admin to review.

Braid attachments linked to Projects or Time Entries map to monday.com File columns on Items. For attachments stored in external systems, we map the file URL to a Text column as a link reference. Large binary attachments (for example, project deliverables over 500 MB) are flagged for the customer to migrate via their own cloud storage integration post-migration.

Braid invoicing and billing records do not migrate to monday.com because monday.com lacks a native accounting or invoicing module. We preserve the invoice reference number, linked Client, amount, and status as a text-exported CSV for the customer's finance team to import into their accounting system post-migration. Budget-versus-actual financial data (not invoicing) does migrate as documented above.