Migrate from Streamtime to Jira

Streamtime Jobs map to Jira Projects as the primary container. For Jobs with a hierarchical sub-structure (nested To-Dos or sub-Jobs), we map the parent Job to a Jira Epic within the destination Project, with child Jobs mapped to Stories or sub-Epics depending on the depth. Job name, description, start date, and due date migrate to Project or Epic fields. Job status (Active, Completed, On Hold) maps to Jira Project category or Epic status. Template Jobs migrate as standard Projects or Epics; the template flag is recorded in a custom field for the admin to configure as a Jira template post-migration.

Streamtime To-Dos map to Jira Issues with the type determined during scoping: tasks map to Jira Task, design or creative items map to Story, and flagged or overdue items map to Bug or Task depending on the customer's naming convention. We preserve parent-child hierarchy by setting the Jira Issue's Parent field to the Epic (from the Job mapping). To-Do completion status maps to Jira Issue Status (To Do, In Progress, Done), and To-Do assignees map to Jira Assignee via email-based User resolution.

Streamtime Companies map to Jira Organizations if the destination Jira site has the Organizations feature enabled (Jira Premium or Enterprise). Otherwise, we map Companies to a custom field (Client__c) of type text or select on the Project or Epic level. Company address, contact name, and client-specific rate card reference migrate as fields on the Organization record or as Project-level custom fields. Jira Organizations do not support the same financial associations as Streamtime Companies, so client billing relationships are documented for the admin to configure in the external billing tool.

Streamtime Team Members map to Jira Users by email address. We resolve each Team Member's Jira account during the migration window. If a Team Member has no Jira account, they enter a reconciliation queue for the customer's Jira admin to provision before the Team Member's assigned Issues are imported. Team Member roles (e.g., Designer, Developer) do not have a native Jira equivalent; we store role metadata in a custom field (Team_Role__c) on the User record or map it to Jira Project Roles if configured.

Streamtime Time Entries map to Jira as structured data rather than native Jira records because Jira Software does not include a native time-tracking object in its standard configuration. We create a custom field Duration_hours__c (number) on the target Issue type and write Time Entry hours, date, and notes as values linked to the correct Jira Issue. The full time entry log (who logged, how long, what notes) is also written as a Jira Comment on the Issue for human readability. Budget burn data from Streamtime migrates as a Project-level custom field (Budget_Burn__c) for reporting. Jira Premium's native time-tracking app or a third-party app (Tempo Timesheets) can be configured post-migration to replace this flat-field approach.

Streamtime Schedules represent team member allocations to Jobs for a given period. Jira does not have a native scheduling or resource-allocation object. We export Schedule data as a structured CSV reference document keyed to Job and Team Member, listing allocation hours and date ranges. The customer's Jira admin uses this as a guide to configure Project Roles, component assignments, or sprint-based workload planning post-migration. We do not create Jira Sprint records from Streamtime Schedules because the sprint cadence and issue-to-sprint mapping do not exist in Streamtime data.

Streamtime Rate Cards define pricing by role, client, or item with multi-currency support. Jira has no Rate Card equivalent. We export Rate Card definitions as a structured reference document listing each role, rate, currency, and Company association. The customer's admin maps these to a custom field set on the Project or Epic level (e.g., Hourly_Rate_Designer__c, Hourly_Rate_Developer__c) or to an external billing tool integrated with Jira. Multi-currency Rate Card rates migrate as decimal values with currency metadata, not as Jira currency fields.

Streamtime Quotes are commercial documents with line items, pricing, and status tied to Jobs. Jira has no native Quote object. We do not migrate Quotes as Jira records because no equivalent schema exists. We export Quotes as structured records in the migration deliverable package and flag them for the customer's admin to rebuild in a dedicated quoting or invoicing tool (e.g., Scoro, HoneyBooks, or a custom ERP). Quote-to-Job associations are preserved in the export for reference.

Streamtime Invoices are commercial documents tied to Jobs and Time Entries with line items, amounts, currency, and payment status. Jira has no Invoice equivalent. We do not migrate Invoices as Jira records. We export Invoice data as structured records in the migration deliverable package and flag them for the customer's admin to rebuild in an external accounting or invoicing tool. Historical invoice-to-Job associations are preserved in the export for audit purposes.

Streamtime Purchase Orders represent outbound vendor commitments tied to Jobs. Jira has no native PO object. We do not migrate POs as Jira records. We export PO data as structured records in the migration deliverable package and flag them for the customer's admin to handle in a procurement or accounting tool. PO-to-Job associations are preserved in the export for audit.