Interviewee:
Aleksandr Knjazetski, Engineering Manager at Bondora
About Bondora:
Bondora is a European peer-to-peer lending platform that facilitates lending and borrowing between individuals. It was founded in 2008 and is headquartered in Estonia. Bondora operates in several European countries and provides an online platform where investors can lend money directly to borrowers, bypassing traditional financial intermediaries like banks.
On Bondora’s platform, individuals can invest in personal loans and earn interest on their investments. Borrowers, on the other hand, can access loans for various purposes such as debt consolidation, home improvement, or funding business ventures. Bondora facilitates the loan origination, repayment, and the overall management of the lending process.
Investors have the opportunity to diversify their investment portfolio by selecting different loan products, borrowers, and risk categories. The platform employs credit scoring algorithms and risk assessment models to evaluate borrowers’ creditworthiness and assign appropriate interest rates.
What is the purpose of Asana to Jira migration?
The purpose of migrating from Asana to Jira is to leverage the benefits and features that Jira offers, particularly in project management and integration with other Atlassian products.
Migrating from Asana to Jira can streamline project management processes, improve collaboration within teams, and leverage the broader capabilities of the Atlassian ecosystem, making it an attractive choice for organizations seeking a robust and integrated project management solution.
What is the scope of Asana to Jira migration?
The scope of migration that we dealt with in Bondora includes the migration of all company’s functions, teams, and projects to Jira. We aimed to migrate the following teams to Jira: Software Engineering & Technology, Data, Analytics, Product, Risk, Legal, Finance, Compliance, Expansions, and Marketing.
The company had 15 years of history in Asana and therefore the amount of data that needed to be migrated to Jira is big.
Which internal team identified the need for this integration: Developers or Business?
The need for integration was identified by Engineering & Technology teams and as it is important to deal with projects we have in one tool then we decided to move the company to Jira & migrate all the data from Asana to it.
What are the key criteria for the migration project to be deemed successful?
All the internal teams are moved from Asana to Jira. Jira project setup & configuration are done according to the needs of each team. All the tickets from relevant projects in Asana migrated to Jira preserving the data in all custom fields.
What factors are critical when selecting a Vendor to work with?
When we selected a vendor for tickets/data migration from Asana to Jira we considered next points:
- easy & understandable way to create integration between 2 tools.
- possibility to map custom fields.
- ability to check logs & errors if there are any.
- opportunity to migrate attachments and comments.
- create a hierarchy for tasks & sub-tasks when doing the migration.
What other tools were you considering, and why did you ultimately choose Getint?
We checked different tools that were available for integration & migration of the tasks in Atlassian Marketplace but Getint seemed to be the most user-friendly and had all the functions that are mentioned above to fulfill the needs that we had.
