Migration guide
From vibe-coded prototype to production
Moving an app feels big until you know what to check. These four questions help you size the work in an afternoon.
Free, and we take one app at a time.
What sets the size
Four questions decide the size of it
Answer these and we can tell you what your move looks like. Skip them and any estimate is a guess.
01
Which screens people use
List the screens people open every day. Old or unused pages usually do not matter.
02
What happens after a click
Saving a form is simple. Pricing orders, sending emails, or booking slots takes more work.
03
What data needs to move
A few test rows are easy. Years of customer records need more care.
04
How people sign in
Email and password is simple. SSO or custom roles need a closer look.
Why it is free
The rebuild is cheap because the parts already exist
A migration usually means a developer studies your app, rebuilds the screens, copies the logic, and moves the data by hand. That takes time, so agencies often charge thousands for it. Orbit works differently. Our agents build the new app, while a person reviews your current app, explains what needs to be built, and checks the result.
That removes a lot of manual typing. The work still needs care, but it is fast enough for us to offer it for free while we learn where migrations get difficult. If an app cannot be moved directly, we rebuild it the same way on Orbit. The price stays the same: free.
What to bring
Gather these before you write to us
A way in
A repo link if your platform gives you one, or half an hour to walk us through the app if it does not.
Your data, or a sample
A CSV export tells us the shape of what you hold. A few rows are enough to start.
The five screens that matter
Name the ones your people open every day. That list scopes the move more than anything else you send.
Before you decide
Some apps should not move
Some apps are harder to move. Heavy realtime features, deep third-party integrations, or a login setup Orbit does not support can make the move less useful. If we see that early, we will tell you. We do not want to replace your app with something worse. No one has gone through this process yet, so you would be first, and we will be clear about what that means.
Questions, answered
Why is the rebuild free?
Because Orbit's agents do most of the building. A person reads your app and directs them, so a rebuild costs us hours rather than weeks. That is cheap enough to give away while we learn where migrations break.
What decides how long it takes?
Four questions: how many screens people genuinely use, how much logic sits behind them, how much live data must come with you, and how unusual your sign-in is. The rest is detail.
What if my app cannot be ported?
Then it gets rebuilt instead, which is the normal path for anything that does not hand over code. We describe your app to Orbit's agents and build the Orbit version of it, at no cost to you.
Do I have to stop using my current app?
No. Run both for as long as you like. Nothing switches over until you point your domain at Orbit.
What makes an app a bad fit?
Heavy realtime, unusual third-party integrations deep in the logic, or a login scheme your business depends on that Orbit does not offer. We will tell you when we see one rather than take the work on.
Answer the four and we can tell you
Share what you have, and we'll explain what moving would involve. If Orbit is not the right fit, we'll tell you why.
Free, and we take one app at a time.
Made in Orbit