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

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

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

Author: Fabien RAYNAUD

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

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>), [Front end](<https://devfeed.tech/topics/frontend.md>)

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

## AI overview

Part 1 of a three-part article shares a personal experience conducting a technical migration to Next.js at JobTeaser. It covers securing sponsorship and time, organizing the project, preserving developer experience, and a timeline involving an audit, production ecosystem, and first use case.

## Source excerpt

Conduct a technical migration within less than 6 months -- Part 1based 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 Timeline of the migration 🔍 Concrete "real life" timing 2 weeks to build an audit in August, done in autonomy and presented to frontend chapter, management, and tech leadership 3 months to put a minimalist ecosystem into production, from November to January, done mainly in autonomy with the help of the Devex and Infra team, and also from hyped frontend engineers 2 months for the release of the first "real life" use case, from February to March, by a squad of 3 engineers + 2 others squads starting their own features on the new stack Buying time and sponsorship to do the migration The first step is buying time and sponsorship for the migration. This is essential to ensure that the necessary resources and funding will be available for the initiative, aka the right environment, to perform the migration properly. This part is more about digging into the pros and cons of this migration and being able to explain it so people will ack