#Migrate from Medusa V1 to medusa V2 ?

18 messages · Page 1 of 1 (latest)

ripe cliff
#

Hello everyone,

I’m currently running Medusa V1 for a second-hand clothing consignment service with extensive customizations. I’m considering migrating to Medusa V2 and would like to know what to expect during the process.

Does anyone know if there’s a migration guide or any documentation available that covers the upgrade steps, potential challenges, and best practices?

Thank you in advance for your help!

dawn anvil
#

Can't migrate to Medusa V2

ripe cliff
#

Conversion ? Are we stuck ?

uneven olive
#

Cannot migrate. Need to set up from scratch

next aurora
#

V2 is entirely different framework and mental model. If you are looking at switch weight your pros and cons for the needing to migrate if the relatively short deadline, if its an eventual shift, I would suggest plan the migration in phases because you might be up for a lot of boilerplate code and a lot of models

ripe cliff
#

How can we trust medusa in the future

#

Why not shifting to an other framework trustworthy if we need to setup from scratch ! 😖

waxen nova
#

Hi, I am currently migrating from v1 to v2 on a fairly standard e-commerce setup without too much customization. I started with a fresh stack and am migrating legacy data using postgres_fdw (Foreign Data Wrapper).

I manually set up the new database (user, region, store, tax, sales channel, etc.) from the admin dashboard, and for the rest, I’m using GPT to help me migrate the data structure from the old version to the new one.

CREATE EXTENSION postgres_fdw;
CREATE SERVER source_server FOREIGN DATA WRAPPER postgres_fdw 
OPTIONS (host 'hostname', dbname 'source_db');

CREATE USER MAPPING FOR current_user SERVER source_server 
OPTIONS (user 'username', password 'password');

CREATE FOREIGN TABLE foreign_table (columns) 
SERVER source_server OPTIONS (table_name 'source_table');

INSERT INTO target_table SELECT * FROM foreign_table;

The structure is changing a bit, especially for authentication, customers, and orders, but overall, I managed to do this on my own in 2-3 days, but as I mentioned, it’s a fairly standard e-commerce setup. Despite having a lot of data, there isn’t much customization.

I’m now in the process of switching my front end. It’s taking a bit more time, but with the documentation and starter packs, it should be fine.

severe laurel
waxen nova
#

I’ve started a documentation that I’ll be happy to share once it’s finished!

burnt radish
#

is your documentation completed? @waxen nova

waxen nova
#

Hey, WIP, almost finished, I'll ping here when it's ready

ripe cliff
#

Waiting for it 🙂 please !

#

@waxen nova

waxen nova
#

Hi, many people have been asking about this.
I haven't had much time to devote to it, but I had started the article before several other things came up. Sorry about that!
Here's the initial draft of the article - it's completely a work in progress that I'll be updating throughout the week.
Feel free to submit PRs if you'd like and share your feedback with me.
https://www.bqst.fr/migrate-from-medusa-v1-to-v2/
https://github.com/bqst/bqst.github.io/blob/master/_posts/2025-03-22-migrate-from-medusa-v1-to-v2.markdown

GitHub

My personnal website. Contribute to bqst/bqst.github.io development by creating an account on GitHub.

ripe cliff
#

Thank you

haughty plinth
#

@waxen nova Thanks for the documentation! Have you had a chance to write any updates to it?

worldly perch