Asana

Jira

Integration

Bondora's Move from Asana to Jira

Bondora, a leading European peer-to-peer lending platform founded in 2008, migrated 15 years of Asana data—including thousands of tasks, subtasks, comments, attachments, and custom fields—to Jira Cloud using Getint. The phased migration preserved full historical context and allowed live Asana use alongside Jira Golden Path rollout. Engineering Manager Aleksandr Knjazetski noted how the team benefited from improved project visibility and tool consolidation through the process.

Find Out how we did it!

Client Overview

Industry:

Fintech

Company size:

Mid-market

Location:

Estonia

KEY STAKEHOLDER

Aleksandr Knjazetski

Engineering Manager at Bondora

Estonian fintech platform supporting peer‑to‑peer lending
Migrated from Asana to Jira Cloud for enterprise-grade project management
Transferred 15 years of historical data across multiple teams
Preserved tasks, subtasks, comments, attachments, and custom fields
Executed phased rollouts to maintain operational continuity

Scope of Work

Phased Historical Data Import

Migrated 15 years of Asana history over staged rollouts to limit disruption.

Full Content Preservation

Transferred tasks, subtasks, custom fields, comments, attachments, timestamps, and relationships.

Live Asana Operation

Enabled teams to continue using Asana while Jira was populated through Getint.

Jira Configuration & Enablement

Configured Jira projects, workflows, custom fields, and dashboards for each team during migration phases.

Integration Objective

To consolidate project management within Jira by migrating 15 years of Asana data—preserving historical context, enabling concurrent tool usage, and setting up enterprise-grade work tracking for diverse teams.

Data Integration Specifics

Issue Types:

Migrated entity types:

Asana Tasks & Sub-tasks → Jira Issues & Sub-tasks

Field Mapping:

Fields and metadata synchronized:

Summary, Description
Custom Fields, Timestamps
Comments & Attachments
Task hierarchy (parent/child relationships)
Assignees

Scripting and Custom Development Support

Migration configured via UI field mapping with guidance; no scripting required.

Success Metrics

The integration’s success was defined by

Historical Data Retention
All 15 years of Asana data preserved, ensuring auditability.
Live-Tool Continuity
Phased delivery allowed uninterrupted Asana use.
Streamlined Onboarding
Jira configured per team with custom workflows and dashboards.
Enhanced Reporting
Teams gained unified visibility through Jira’s reporting capabilities.

Vendor Selection Process

Bondora chose Getint over CSV/manual export and other tools because it could preserve full task history, comments and attachments, support field mapping, show logs, and enable phased migration while maintaining Asana usage.

Why Getint Stood Out?

During the vendor selection process, Getint emerged as the preferred choice due to:

Built-in Integration

No need for an external hub, ensuring easier maintenance

User-Friendly Interface

Accessible for standard Jira administrators, with straightforward configuration

Reliability and Low Maintenance

Set-and-forget functionality

Cost-Effectiveness

Balanced pricing for the value delivered

Responsive Support

Prompt and effective assistance during setup and troubleshooting

800 000 +

Active Users

5 000 +

Installations

3.8 / 4

Rating

7 mln

Integrations Daily

Our Certifications

What We Accomplished

Migrated 15 years of Asana data

across all teams.

Full context preserved,

including files, comments, fields, and timestamps.

Maintained live Asana operation

during Jira deployment.

Custom Jira setup per team

with workflows, fields and dashboards for smooth operations.

What Key Stakeholder Say

“Getint … has easy way of setting up integration between the systems and a user‑friendly interface to create field mapping… possibility to migrate attachments and comments.”

Aleksandr Knjazetski

Engineering Manager at Bondora

Conclusion

Getint enabled Bondora to unify 15 years of Asana history into Jira Cloud—preserving data, minimizing disruption, and empowering teams with enhanced tool capabilities.

Through phased migration and rich context mapping, the migration became a strategic transformation for cross-functional collaboration and operational visibility.

Schedule a Free Demo with our Integration Expert

Discover how seamless and efficient integrations can be with a personalized demo. Our expert will walk you through the process, tailor the session to your specific needs, and answer any questions you have about connecting your tools effectively.

Book a Demo Call

Frequently asked questions

Have questions? 
We've got you!

Our comprehensive FAQ section addresses the most common inquiries about our integrations, setup process, pricing, and more - making it easy to find the answers you need quickly.

Can we migrate 15 years of Asana history?

Yes—Bondora migrated 15 years worth of tasks, subtasks, comments, attachments, timestamps, and custom fields from Asana to Jira.

Will Asana remain usable during migration?

Yes—Getint supports phased migrations to allow concurrent use of Asana during Jira deployment.

Are attachments and comments included?

Yes—all comments, attachments, and metadata were preserved.

Do we need scripting or extra tools?

No—all mapping and migration was handled via Getint’s UI; no scripting required.

Can Jira be configured per team during migration?

Yes—Jira workflows, dashboards, and custom fields were tailored during the phased rollout.

Experience a smarter way to integrate & synchronize.

Discover the power of seamless connections, bridging your favorite tools for optimized workflow and productivity. Unleash the potential of unified platforms with Getint.

Book a Demo