# Conduct a technical migration within less than 6 months -- Part 2

DevFeed: [Conduct a technical migration within less than 6 months -- Part 2](<https://devfeed.tech/articles/conduct-a-technical-migration-within-less-than-6-months-part-2-20094.md>)

Original publisher: [Read original article](<https://medium.com/jobteaser-dev-team/conduct-a-technical-migration-within-less-than-6-months-part-2-c4f2cd1feea4?source=rss----bd77d16a0035---4>)

Author: Fabien RAYNAUD

Published: 2024-12-02T09:46:56Z

Content type: tutorial

Language: en

Sources: [JobTeaser](<https://devfeed.tech/sources/jobteaser.md>)

Topics: [migration](<https://devfeed.tech/topics/migration.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [maintenance](<https://devfeed.tech/topics/maintenance.md>)

Tags: [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [migration](<https://devfeed.tech/tags/migration.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [nextjs](<https://devfeed.tech/tags/nextjs.md>), [project-management](<https://devfeed.tech/tags/project-management.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

## AI overview

Part 2 of a three-part article about conducting a Next.js technical migration at JobTeaser. It focuses on organizing the migration project by defining a realistic MVP scope, prioritizing tasks, assigning work, communicating progress, and setting deadlines.

## Source excerpt

Conduct a technical migration within less than 6 months -- Part 2based on Next.js migration, performed at JobTeaser What is this 3-parts article about: sharing my own experience with handling a technical migration 📖 some additional elements that I find relevant and could help (identified with 📖 emoji) but not personally tested What this presentation is NOT about: technical step-by-step Next.js migration the perfect and only way to do a migration I tried to be as exhaustive as possible, but I didn't even complete all the points personally. So the presentation is a mix of my personal experience and all the things that could help to do it "qualitatively". Pick what is necessary for you and your ecosystem. 3 main parts: Buying time and sponsorship to be able to perform such a migration = creating a good environment to navigate easily to success ▶ Organize your project = keep an eye on and communicate about what was done and what needs to be done Preserve the developer experience = ensure use, sustainability, and future maintenance of the migration Now that you have convinced the right people and made a big-picture plan, time to jump into the project, whether you are part of the implementation team or not. Organize your project The second step is to organize the project. This includes cleaning the scope of the migration regarding the most important tasks and secondary ones that could be done later. It's also about having a clean place to organize, prioritize, and communicate the project execution. Define the "real" scope of the migration = MVP with only the mandatory tasks: Be prepared for the next steps. You won't be able to perform all the tasks from the initial plan by yourself or with the initial team, only the most important ones Listing and specifying secondary tasks is important for the next steps of the project (after the migration) Continue your technical watch on the subject and adjust the migration if necessary, nobody wants an already deprecated solution. A