Skip to content

Migration from Jira

Move from Jira to Kiket while keeping workflows, boards, and history under source control. Kiket provides two approaches for Jira integration:

  1. Import Wizard (builtin) - One-time data migration with AI-powered field mapping
  2. Jira Extension - Ongoing bidirectional sync for teams maintaining both systems

Choosing Your Approach

Scenario Recommended Approach
Full migration to Kiket, retiring Jira Import Wizard
Running Kiket and Jira in parallel Jira Extension
Gradual migration with ongoing sync Jira Extension → Import Wizard
One-time import of historical data Import Wizard

Option 1: Import Wizard (Builtin)

The Import Wizard provides a guided, AI-assisted migration from Jira to Kiket. Access it from Settings → Import Data.

Features

  • AI-powered field analysis - Automatically analyzes your Jira schema and suggests field mappings
  • Status mapping - Maps Jira statuses to Kiket workflow states
  • Issue type mapping - Maps Jira issue types to Kiket types
  • Deduplication detection - Identifies potential duplicates before import
  • Preview mode - Review what will be imported before committing
  • Batch processing - Handles large projects efficiently

Step 1: Connect to Jira

  1. Navigate to Settings → Import Data
  2. Select Jira from the available providers
  3. Enter your credentials:
  4. Jira URL: Your instance URL (e.g., https://company.atlassian.net)
  5. Email: Your Jira account email
  6. API Token: Generate at Atlassian API Tokens

Step 2: Select Project

After connecting, you'll see a list of accessible Jira projects. Select the project to import.

Step 3: Review AI Analysis

The wizard analyzes your Jira project and provides:

Analysis Description
Schema Analysis Overview of custom fields, issue types, and workflows
Field Mappings AI-suggested mappings from Jira fields to Kiket fields
Status Mappings Suggested workflow state mappings
Issue Type Mappings Suggested issue type conversions
Deduplication Results Potential duplicates with existing Kiket issues

Review and adjust the suggested mappings as needed.

Step 4: Preview Import

Before importing, preview a sample of issues to verify:

  • Issues that will be created vs. updated
  • Mapped statuses and types look correct
  • Field values are transformed properly

Step 5: Execute Import

Run the import. The wizard provides real-time progress:

Import Progress
├── Created: 142 issues
├── Updated: 8 issues
├── Skipped: 3 issues (duplicates)
└── Duration: 45 seconds

Step 6: Verify Results

After import:

  1. Spot-check a sample of imported issues
  2. Verify attachments transferred correctly
  3. Check that comments are preserved
  4. Validate workflow states are correct

Option 2: Jira Extension (Bidirectional Sync)

For teams running Kiket and Jira in parallel, the Jira Extension provides ongoing bidirectional synchronization.

Installation

  1. Go to Settings → Installed Extensions
  2. Find Jira Integration in the marketplace
  3. Click Install
  4. Configure secrets:
  5. JIRA_URL - Your Jira instance URL
  6. JIRA_EMAIL - Authentication email
  7. JIRA_API_TOKEN - API token
  8. JIRA_WEBHOOK_SECRET (optional) - For webhook verification

Features

Feature Description
Bidirectional Issue Sync Changes in either system sync automatically
Status Sync Workflow transitions sync via webhooks
Comment Sync Comments stay synchronized
Attachment Mirroring Files sync between platforms
Field Mapping Custom field synchronization
Command Palette Quick actions (⌘K): "Sync with Jira", "View in Jira"

Configuration

After installation, configure per-project settings:

# Sync direction options
sync_direction: bidirectional  # or jira_to_kiket, kiket_to_jira

# Feature toggles
sync_comments: true
sync_attachments: true
auto_create_mappings: false

Setting Up Jira Webhooks

For real-time sync, configure Jira webhooks:

  1. Go to Jira Settings → System → WebHooks
  2. Create a new webhook pointing to your Kiket extension endpoint
  3. Select events: issue_created, issue_updated, comment_created, comment_updated
  4. Add webhook secret for signature verification

Commands

The extension adds commands to the command palette (⌘K / Ctrl+K):

  • Sync with Jira - Manually trigger sync for current issue
  • Map to Jira Issue - Create mapping to existing Jira issue
  • View in Jira - Open the mapped Jira issue
  • Sync Jira Project - Trigger full project sync
  • Export Mappings - Export issue mappings as CSV

Concept Mapping Reference

Jira Kiket Notes
Projects Projects Backed by Git repositories
Workflows .kiket/workflows/*.yaml Version-controlled workflow definitions
Boards .kiket/boards/*.yaml Kanban/Scrum board configurations
Issue Types Issue Type Definitions Configured per-project
Custom Fields Custom Fields Schema defined in project settings
Jira Automation Workflow Actions Declarative automation in YAML
Post Functions Extension Webhooks Event-driven automation
Notification Schemes Notification Preferences Per-user channel preferences
Filters/JQL Saved Views Saved filter configurations

Migration Checklist

Before Migration

  • Export Jira workflows, issue types, and custom fields for reference
  • Document board configurations, swimlanes, and filters
  • Identify automations that need Kiket equivalents
  • Create target Kiket project with appropriate workflow
  • Test import with a small sample first

During Migration

  • Connect to Jira and verify project access
  • Review AI-suggested field mappings
  • Adjust status mappings to match Kiket workflow
  • Preview import results before committing
  • Run import in batches for large projects

After Migration

  • Verify sample of imported issues for accuracy
  • Check attachments and comments transferred
  • Validate board column counts and WIP limits
  • Configure workflow actions to replace Jira automation
  • Update team documentation and notify users

Troubleshooting

Import Wizard Issues

Connection Failed - Verify Jira URL includes https:// - Check API token is valid and not expired - Ensure account has project access

Field Mapping Errors - Review AI suggestions and adjust incompatible mappings - Check field types are compatible (e.g., number → number) - Custom fields may need manual mapping

Missing Issues - Check JQL filters in Jira project - Verify account has permission to view all issues - Sub-tasks require include_subtasks: true option

Extension Sync Issues

Sync Not Working - Verify project is registered in extension settings - Check sync_enabled is true for the mapping - Review sync job logs for errors

Webhook Not Processing - Verify webhook URL is accessible from Jira - Check webhook secret matches configuration - Review Jira webhook delivery logs

Status Sync Failing - Ensure all Jira statuses are mapped - Check Kiket workflow allows the target transition - Verify sync_on_transition is enabled

Next Steps

After migrating from Jira:

  1. Configure Workflows - Set up .kiket/workflows/ to match your process
  2. Create Boards - Define boards in .kiket/boards/
  3. Set Up Automation - Replace Jira automation with workflow actions
  4. Install Extensions - Add integrations (Slack, GitHub, etc.)
  5. Train Your Team - Share the new workflow with your team

Migrating to Kiket centralizes your workflow configuration in Git and unlocks automation as code.