Migrate from Smartsheet to Jira

Smartsheet Workspaces are top-level organizational containers. During migration, we map Workspace hierarchies to a single Jira Cloud organization or, for very large migrations, to multiple Jira projects grouped by team. Workspace-level sharing settings and permission structures do not map directly to Jira's project-level permissions and require a separate permission redesign during scoping.

Smartsheet Folders within a Workspace may map to multiple Jira Projects (one per product or team) or to Components within a single Jira Project (for work areas within a shared project). We determine the split strategy during scoping based on the customer's sprint cadence and team ownership. Folder naming conventions migrate as project or component names.

Smartsheet Sheets are the primary project container and map to Jira Projects. Each Sheet's primary column becomes the issue summary field, and column types inform the Jira issue type assignment. A Sheet with predominantly task-like rows (with assignees, due dates, and status columns) maps to a Jira project with a Kanban or Scrum board. We pre-create the Jira project schema before migration, including the issue type scheme (Story, Task, Bug, Epic), workflow states, and any required screen configurations.

Smartsheet rows migrate to Jira issues. We infer the Jira issue type from column content signals: rows with Story Points columns, sprints, or agile-specific labels map to Jira Stories; rows with a parent hierarchy or sub-tasks map to Epics and Subtasks; rows marked as bugs in a Status column map to Jira Bug issue type. Row order within the Smartsheet sheet is preserved as the Jira issue rank or backlog ordering. The primary column value becomes the Jira Summary field.

Smartsheet Contact List columns (containing user email addresses) map to Jira's Assignee field. We resolve each Smartsheet contact email to the corresponding Jira user account by email match. If a Jira user does not exist for a contact, we hold those rows in a reconciliation queue pending account provisioning. Smartsheet Reporter or Created By columns map to Jira's Reporter field when the column type is identified as a user reference.

Smartsheet Date columns migrate to Jira standard fields (Due Date, Start Date) or to custom date fields depending on column naming. Date-only columns migrate cleanly. Columns named 'Start Date' map to Jira Start Date; columns named 'Due Date' or 'End Date' map to Due Date. We verify date format consistency during transformation because Smartsheet stores dates as ISO-8601 but export formats can vary.

Smartsheet predecessor relationships (dependency links between rows) migrate as Jira issue links. We build a lookup table mapping each Smartsheet row ID to its Jira issue key during the row migration phase, then create Blocks or is Blocked By issue links using the resolved Jira keys. Jira Automation for Jira Cloud (or ScriptRunner for Data Center) can be used to rebuild Smartsheet-style predecessor scheduling, but this requires manual configuration post-migration. Critical path flags from Smartsheet Baseline columns do not migrate automatically.

Smartsheet Dropdown List columns map to Jira single-select custom fields if the options are a fixed set of values. Multi-select columns in Smartsheet map to Jira Labels or multi-select custom fields. During scoping, we assess whether the dropdown values are a closed set (suitable for a picklist) or an open set (suitable for Labels). Jira's Labels field accepts any text value without admin configuration, making it the lower-risk mapping for Smartsheet columns used as flexible tagging fields.

Smartsheet formula columns (cross-sheet references, conditional logic, aggregations) do not migrate as live computed values because Jira does not support formula fields in the same way. We flag every formula column during discovery, document its calculation logic, and recommend a replacement approach: either a Jira custom script field, a Jira Automation rule, or a post-migration reporting solution. Simple numeric formulas (SUM, AVG, COUNT across rows) may map to Jira ScriptRunner custom fields if the customer has a Data Center license.

File attachments on Smartsheet rows and sheets are downloaded from Smartsheet's attachment endpoints and re-uploaded to the corresponding Jira issues via the Jira REST API. Jira Cloud enforces a 10 MB per-file attachment limit. We flag any attachments exceeding this limit during discovery. The original Smartsheet-hosted attachment URLs break after migration; we re-attach files to Jira issues under the original uploader's Jira account when possible.

Smartsheet row-level and sheet-level discussions migrate to Jira issue comments. Threading structure in Smartsheet (nested replies) flattens into a linear comment sequence in Jira's standard comment model. Discussion authors map to Jira users by email match. The comment body migrates as plain text; rich text formatting in Smartsheet discussions is preserved where Jira's Atlassian Document Format supports it.

Smartsheet automations (workflow rules with triggers and conditional actions) are not accessible via Smartsheet API and cannot be exported. We document every automation configuration during discovery, capturing the trigger event, conditional criteria, and action set. The deliverable is a written automation inventory with Jira Automation for Cloud rule equivalents documented step-by-step. The customer's Jira admin rebuilds these rules post-migration. Automations are not migrated as code or configuration.