Migrate your Accolade data

Portfolios are top-level organizational containers in Accolade. We export portfolio metadata, linked projects, budget allocations, and strategic alignment tags intact. No transformation is required when the destination supports a hierarchical portfolio model.

Projects are the primary execution units linked to a portfolio. We extract all standard fields including stage, status, owner assignment, start and end dates, and custom properties. Relationships to parent portfolio and child work packages are preserved via foreign key mapping.

Innovations represent early-stage ideas submitted through the platform. The schema includes submission date, originator, scoring attributes, and workflow state. Where the destination has no equivalent object, we merge these into Projects or a custom Ideas object and preserve the original Innovation_ID as a reference field.

Business Units are organizational entities used for segmentation and reporting. We map these to Companies or Divisions in the destination. Multi-level BU hierarchies are flattened during export and reconstructed using parent-child lookup fields in the target system.

Accolade supports user-defined fields on Projects and Innovations. We extract the full schema including field type, required flag, and picklist options. At import time, we create matching custom fields in the destination if the platform supports them, or store the data as structured JSON in a fallback property.

Documents and files attached to projects and innovations are exported with their original filenames, MIME types, and content. We transfer binary blobs directly and re-attach them to the corresponding record in the destination system.

Accolade uses configurable workflow stages with gate approvals. Each stage has a name, order, and optional approver assignment. We export the full stage definition including transition rules and recreate the pipeline structure in the destination, mapping stage names to equivalent statuses.

User accounts include name, email, role, and BU assignment. We export the user roster and map Accolade roles to the closest permission model in the destination CRM or PM system. Active licenses and deprovisioned accounts are flagged separately so the customer can decide whether to create inactive placeholders.

Audit comments and activity history are stored as timestamped entries linked to a project or innovation. We export these as a flattened feed. Where the destination has a native activity log, we append the entries; otherwise, we store them as a JSON array on the target record.

Accolade tracks quantitative metrics against projects such as budget consumed, schedule variance, and custom KPIs. These are numeric time-series values. We export them as structured key-value records and map them to custom numeric fields or a linked Metrics object in the destination.