Migrate from WiseTeam to Jira

WiseTeam Projects map to Jira Projects. Each WiseTeam Project carries a name, description, status, and links to a Client record. We map Project name and description directly to Jira Project name and description. The parent Client relationship is preserved as a Jira custom field (ClientName__c) or as a Jira label prefix since Jira Projects do not have a native parent-client lookup. We provision Jira Projects before any Issues insert so that the Project key is available for Issue parent-project references.

WiseTeam Tasks map to Jira Issues. Task title becomes Issue Summary; Task description becomes Issue Description (stored as plain text or Atlassian Document Format depending on the Jira version). Task status maps to a Jira Status that belongs to the Workflow assigned to the destination Project. Sub-tasks (Tasks nested under Tasks in WiseTeam) map to Jira Sub-Tasks, which require the parent Issue to exist before the Sub-Task inserts. We order the load to resolve parent Issue IDs before Sub-Task creation.

WiseTeam Time Entries map to Jira Worklogs on the target Issue. Each Worklog carries hours, date, and description from the WiseTeam Time Entry. The destination Jira Project must have time-tracking enabled before migration; if it does not, we flag it during scoping and recommend enabling it in the destination project configuration. Jira Worklog authorship is set to the User resolved from the WiseTeam user's email address.

WiseTeam custom fields on Projects and Tasks map to Jira custom fields of equivalent type. We discover custom field names, types, and picklist values during scoping. Jira requires custom fields to be created per project context (team-managed vs company-managed project types have independent field scopes), and they must be added to the relevant Issue Screen and Field Configuration before the mapped data loads. Global custom fields in Jira require an admin with the appropriate permissions.

WiseTeam Users are assigned as Task owners and Project participants. We resolve WiseTeam users by email address against the Jira destination site's User directory. Any WiseTeam user without a matching Jira User is held in a reconciliation queue for the customer's admin to provision before record import begins. Jira groups and project role assignments are documented as a post-migration configuration item.

WiseTeam Client records (company name, contact details, lifecycle stage) have no direct Jira equivalent because Jira does not have an Account or Contact object. We export Clients to CSV and deliver the export as a separate handoff file. Optionally, we map Client name to a Jira custom field (Client__c) on Issues or as a Label prefix so that project managers can filter issues by client without a separate CRM.

WiseTeam Opportunities (stage, value, close date) do not map to a Jira object. Jira is a work-tracking tool, not a sales CRM. We export Opportunities to CSV with their stage and value data. If the customer needs to preserve opportunity-to-project links, we map Opportunity name to a custom field (OpportunityRef__c) on the corresponding Jira Project as a reference string.

WiseTeam Invoices (line items, amounts, status) have no Jira equivalent. Jira does not include billing or invoicing capabilities. We export all Invoice records to CSV with headers and line items flattened, and deliver the export file to the customer's admin. Invoicing should be handled in a dedicated billing or accounting tool post-migration.

WiseTeam calendar events (synced from iCal, Outlook, and Gmail) carry title, date, and attendee information. Jira does not maintain a separate calendar of external appointments. We map event titles to Jira Issue summaries if events correspond to specific project tasks, and event dates to Issue due dates. Events without a linked Task are exported as a CSV calendar log for the customer's reference.

File attachments on WiseTeam Tasks and Projects migrate to Jira Issue attachments via the Jira REST API. We extract file blobs from the WiseTeam export, upload each to the corresponding Jira Issue, and preserve the original filename and any inline image attachments. Jira has a 32 MB per-file attachment limit; files exceeding this are flagged for manual re-upload with a reference list delivered in the migration handoff.