# Conduct a technical migration within less than 6 months -- Part 3 (final)

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

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

Author: Fabien RAYNAUD

Published: 2024-12-02T09:47:16Z

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>), [Automation](<https://devfeed.tech/topics/automation.md>), [maintenance](<https://devfeed.tech/topics/maintenance.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.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

The final part of a three-part article about conducting a technical migration at JobTeaser, based on the author's experience with a Next.js migration. It focuses on preparing the organization, organizing the project, preserving developer experience, maintaining automation and documentation, and training the team.

## Source excerpt

Conduct a technical migration within less than 6 months -- Part 3 (final)based 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 You are now ready to focus on the implementation but do not hesitate to make a step aside and check if the learning curve is not too big for newcomers on the migrated part. Preserve the Developer's Experience Finally, it is important to preserve the Developer's Experience throughout the migration process. This means minimizing disruption to the development environment and ensuring that developers can continue to work efficiently. It also means preparing the next step of the project (outside migration) and making it efficient as soon as possible. Analyze and preserve the current development environment of the team Check the used tools and the compatibility after the migration, and communicate if you need to remove one Keep automation as much as possible, nobody wants to get back to manual stuff after a migration Take time to document (update) what you are keeping, newcomers would thank you for that Train the team to be