Migrate your Resource Management by Smartsheet data

Sheets are the primary project container in Smartsheet. We export all Rows, Cells, and Column definitions including custom column types. Dependencies between Rows map as predecessor/successor relationships. Exported as-is for Gantt-capable destinations or flattened into task lists for simpler tools.

People objects from Resource Management API contain name, role, availability, and allocation percentages. We map them to the destination's equivalent resource or team-member object, preserving assigned hours and utilization percentages.

Assignments link People to project tasks/rows with allocation hours. Mapping is direct when the destination has a native assignment object; when it does not, we embed allocation data as task-level custom fields.

Phases are hierarchical groupings of tasks within a project. Not all PM tools have a Phase concept. We map them to milestones or parent-task groupings depending on destination schema.

Portfolios aggregate multiple projects and show aggregated capacity and timeline data. We export the portfolio's project list and summary metrics. We do not replicate portfolio-level dashboards natively; those are rebuilt on the destination.

Custom fields exist as column types (Text, Date, Contact List, Dropdown, etc.) attached to Sheets. We preserve column type metadata and values during migration. Contact List fields map to person-type fields on the destination.

Automation rules (triggers, conditions, actions) are not exposed via Smartsheet's public REST API. They cannot be programmatically exported and must be rebuilt manually on the destination platform.

Attachments on rows or sheets are excluded from Smartsheet's export and API responses. Customers must use the Backup tool to download attachments separately before migration; we do not migrate binary attachment files.

Reports aggregate data from multiple Sheets and support CSV export. We export report data as-is when the destination uses a flat data model. Where reports contain computed or filtered views, we migrate the underlying Sheet data instead and note the filter logic in the migration scope document.

Row-level predecessor/successor dependencies are exported as dependency relationships. Not all destination tools model dependencies the same way; we map them to native dependency fields where available or to custom dependency columns.

Resource Management's built-in timer locks entries after one week by default. We export available time entries via the Reports export (CSV) during the discovery phase before that window closes. Entries beyond that window are noted as unrecoverable.

Row-level Discussion/Comments are accessible via API. We export them as thread-style comment objects on tasks where the destination supports them, or flatten them into a task's description field.