Migrate from Accolade to monday Work Management

Accolade Portfolios are top-level organizational containers holding Projects with budget allocations and strategic alignment tags. We map each Accolade Portfolio to a monday.com Workspace, using the Portfolio name as the Workspace name. Portfolio-level budget and strategic alignment tags migrate as custom columns on a top-level Overview Board within the Workspace. Note that monday.com does not have native portfolio roll-up across Workspaces; cross-portfolio reporting requires either monday.com's Enterprise WorkOS Connect feature or a cross-Workspace tag taxonomy that we define during schema design.

Accolade Projects are the primary execution units linked to a Portfolio, containing stage, status, owner, start/end dates, and custom properties. We map each Project to a monday.com Board, preserving the Project name, dates as Timeline columns, owner as Board member, and custom properties as typed columns. Projects with sub-projects in Accolade translate to Groups within the same Board, or to sub-boards linked via monday.com Connect if the customer prefers separate Board scope per sub-project.

Accolade Innovations represent early-stage ideas submitted through the platform, with submission date, originator, scoring attributes, and workflow state. We map Innovations to monday.com Items within the appropriate Board. The Accolade workflow state maps to a Status column; the originator maps to the Assignee column; scoring attributes map to custom Number or Rating columns. Innovations that have been promoted to Projects retain their parent-project relationship through a cross-item Tag or Connect link that we establish during migration.

Accolade Business Units are organizational entities used for segmentation and reporting, with multi-level hierarchies possible. We map each BU to either a monday.com Group within each relevant Board (preferred if BUs align to project groupings) or a Tag applied across Boards (preferred if the same person belongs to multiple BUs). Multi-level BU hierarchies are flattened during export; only the leaf-level BU name is mapped. If BUs also require parent-company reporting, we create a separate BU Overview Board with a Company column linked to parent BU items.

Accolade custom properties are user-defined fields on Projects and Innovations, including field type, required flag, and picklist options. We extract the full schema across all Business Units and create a superset of monday.com custom columns. Each Board receives whichever columns from the superset apply to its record type; columns that have no value for a given item are left null and logged in the field-coverage report. Picklist options in Accolade map to Status or Dropdown columns in monday.com; multi-select picklists map to multi-select columns.

Documents and files attached to projects and innovations in Accolade export with their original filenames, MIME types, and content. We transfer binary blobs directly and re-attach them to the corresponding Items in monday.com. Files over 100MB are chunked during extraction with SHA-256 checksum verification during reassembly. The file manifest logs each attachment's source record, original filename, MIME type, size, and destination item ID for reconciliation.

Accolade workflow stages have a name, order, optional approver assignment, guard conditions, and transition rules per stage. We export the full stage definition and map it to a monday.com Status column with ordered labels matching the stage order. Approver assignments and guard conditions are documented in the workflow inventory and are not migrated as automations; these require rebuild in monday.com Automations or the new workflow builder (legacy automations must migrate by April 30, 2026 per monday.com's deprecation timeline).

Accolade user accounts include name, email, role (Admin, Project Manager, Innovator, Viewer), and BU assignment. We export the user roster and map Accolade roles to monday.com permission levels: Admin maps to Workspace Admin, Project Manager maps to Member, Innovator maps to Member, Viewer maps to Guest. Owner assignments on Accolade Projects and Innovations map to Assignees in monday.com. Any Accolade user without a matching monday.com account is flagged in the reconciliation report for manual provisioning before record migration.

Accolade stores timestamped comments and audit entries linked to a project or innovation. We export these as a flattened feed and append them to the corresponding monday.com Item's Update history in chronological order. Each Update retains the original timestamp, author name, and comment body. Audit entries without a comment body (e.g., status-change events) are logged as Updates with a system-generated description of the change.

Accolade tracks quantitative metrics against projects such as budget consumed, schedule variance, and custom KPIs as numeric time-series values. We export them as structured key-value records and map to monday.com Number columns (for single-value KPIs) or to a separate Metrics sub-board with linked Items if the customer requires time-series tracking. KPI labels become column names; numeric values become column values; date-stamped observations become separate Items or sub-items in the Metrics sub-board.

Accolade's Innovation-to-Project promotion does not always preserve the parent-child relationship in exports. We detect this pattern during schema analysis by matching on creation date, originator, and naming convention, then reconstruct the lineage. For monday.com, we create a cross-item Tag (e.g., #promoted-from-innovation) on the Project Board Item linked to the originating Innovation Item, or use monday.com Connect for bidirectional linking if the Enterprise plan is in scope. Orphaned Innovations without a resolved parent are flagged for customer review before finalizing.

Accolade governance gates specify an approver per stage who must take action before a record can advance. We export the gate-approver assignments as a configuration document. These do not migrate as automations in monday.com because monday.com lacks native approval gate features; instead, we document each gate with its triggering condition, approver, and recommended monday.com automation trigger (e.g., when Status changes to Gate-1, send email to Approver and notify Assignee). The customer's admin rebuilds these as automations post-migration.