There are a few things that you should know about manual migration.
It's not rocket science.
We even did it once in the fifth module of this course,
when we migrated the backend application to the NX mono repository.

In theory, all you need to do is to create a new NX mono repository,
add an empty application and move files into that new application.

In practice, it can be challenging. A lot of things may complicate the process.

---
title: Manual migration of existing applications
description: How to manually migrate complex applications to the NX mono repository
privateVideoUrl: https://stream.mux.com/NpSqzZ9nAaAoyvngI5cUAeWLjYuuTyxUaTK3Ube72dE.m3u8
---

There are a few things that you should know about manual migration.
It's not rocket science.
We even did it once in the fifth module of this course,
when we migrated the backend application to the NX mono repository.

In theory, all you need to do is to create a new NX mono repository,
add an empty application and move files into that new application.

In practice, it can be challenging. A lot of things may complicate the process.

galczo5

How to manually migrate complex applications to the NX mono repository

Manual migration of existing applications

In the previous modules, we used the manual immigration method to migrate our

NES.js application standard NES.js application to NX Monorepo.

And there are a few things that you should know about manual immigration.

First of all, it's not a rocket science. All you need to do is to create a new

and then move some files to new place. In practice, it can be challenging. A

complicate the process and the bigger and more complicated app is, you can have

So in the next few lessons, we'll focus on a few aspects of manual immigration.

We'll focus on potential problems and recommended solutions you may approach

We will discuss preparing the migration plan, a very important step in my

We will consider target architecture after migration and of course, migration

All these lessons will be constructed as collections of tips. All projects are

the person who knows your project the best. And it's very hard or impossible to

list of migration steps that works on all projects. So I want you to not treat

best practices because there's no such thing as the best practice you can have

practices and everything depends on the context. And please be sure that you

app is unique and every app migration process will look different. So we always

about migration as a process in the specific context of your application.

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Masterclasses

Tutorials

Fullstack React with TypeScript