What Matters Is Testing That Doesn't Break: Kakaopay's Jira Migration Retrospective

Kakaopay carried out a migration that extracted only specific projects from the existing Kakao Jira system to build a new environment. Due to security concerns, instead of backing up all data, they adopted an approach that used a Plug-in to selectively move only the necessary data.

To prevent unpredictable errors, they first conducted thorough test migrations. Tasks were selected for testing based on ticket count, volume of attachments, and Workflow complexity, and through this process they identified issues such as Plug-in version mismatches, missing filters and user permissions, and XML parsing errors.

Although a partner company recommended halting the project citing failures in similar cases, Kakaopay decided to proceed with the production migration since they had already secured solutions to the errors through testing. During the actual production migration, they ran into difficulties again when XML parsing errors occurred, but they continued the migration by resolving the issues based on the error-response list they had prepared in advance.