Migrate from Matilda Workspace to Jira

Matilda Teamspaces are the top-level organizational container defining permission boundaries and containing all child objects. We map each Teamspace to a Jira Software Project, preserving the Teamspace name as the Jira Project name and using the Teamspace slug as a basis for the Jira Project Key (auto-generated uppercase prefix for issue keys). Jira Project permission schemes and project roles are configured to approximate the Teamspace's permission model during migration.

Matilda Projects carry start/end dates, status, auto-scheduling, and linked Tasks. We map each Matilda Project to a Jira Epic (Issue Type = Epic) so that the parent-child relationship between Projects and Tasks maps to Epic-Story or Epic-Task in Jira. The Matilda Project name becomes the Epic summary; the Project description migrates to the Epic description field. Project-level custom properties map to Epic-level custom fields.

Matilda Tasks carry assignees, due dates, status, subtasks, and rich-text description. We map top-level Tasks to Jira Story issues and child Tasks to Jira Task issues, with the Jira Epic Link field set to the parent Epic derived from the Matilda Project. Subtasks migrate as Jira Subtask issues linked to their parent Story or Task via the Parent Link field. Task status values map to Jira workflow statuses (To Do, In Progress, In Review, Done) configured per the destination project's workflow scheme.

Matilda subtasks inherit the parent's assignee, due date, and description structure. Jira Subtask is a distinct Issue Type with a Parent Link field. We preserve the subtask hierarchy by creating Jira Subtask issues with the parent Jira Story or Task as the Parent Link. Jira Subtask does not support further nesting (no sub-subtask), so deeply nested Matilda subtask chains are flattened to Subtasks linked to the top-level parent Story.

Matilda's auto-schedule engine infers task sequencing and dependency relationships. Jira uses explicit issue links (Blocks, Blocked By, Depends On, Duplicate, etc.) to represent dependencies between issues. We export Matilda dependency data as Jira Issue Links of type Blocks or Blocked By, creating the link records after the parent issues have been inserted so the link targets exist at the time of creation.

Matilda Docs are rich-text documents embedded within Projects and linked to Tasks. We export doc content as HTML and map it to the Jira Issue description field for Docs directly associated with a single Task. Docs linked to a Project but not a specific Task are flagged for the customer to decide whether to create a Jira Issue to hold the content, export as a standalone HTML file package, or migrate to Confluence (separate product, separate scope). Links between Docs and related Tasks are preserved as Jira issue links or mentioned in the Jira description.

Matilda Chat threads are integrated per-project with messages containing author, content, and timestamp. Jira does not have a native chat thread object. We export chat message content as Jira Issue Comments on the related Jira Epic or Story. The comment author maps to the Jira user by email lookup. Chat threads not linked to a specific Project or Task are exported as a chronological HTML log file for manual reference.

We preserve task assignee and project membership data by resolving Matilda user emails against the Jira Cloud or Data Center user directory. Jira assigns issues to User records; the assignee field accepts a Jira User ID. Matilda users without a matching Jira account are held in a reconciliation queue for the customer's admin to provision before record import resumes. Jira Free tier limits user assignment to 10 users; Standard and above support unlimited users.

Matilda supports custom fields on Projects and Tasks. Custom field types and naming conventions vary by workspace. We inventory all Matilda custom fields during discovery, map them to Jira custom fields of the equivalent type (text, number, date, select, multi-select, user picker), and configure them on the relevant Jira Issue Type Screen so they appear on the Edit and View screens. Jira field context (which issue types and projects a custom field applies to) is set during Jira schema configuration.

Matilda attachments on Tasks and Docs reference files stored in Matilda. We export attachment metadata (filename, URL, uploader, timestamp) and download the file content. Jira Cloud accepts attachments via multipart upload through the REST API (10 MB per file on Standard, 50 MB on Premium and Enterprise). We upload each file to the related Jira issue and preserve the original filename and creation timestamp. Files exceeding Jira Cloud size limits are flagged in the pre-flight report and delivered as a downloadable file package with Jira issue keys documented for manual reattachment.