Migration from Legacy to Dev - Fulfillment Location

Dev Platform
1

Is there any official way to migrate an app from legacy to dev dashboard? I haven’t been able to find a way.

The issue is the Fulfillment Location tied to the app.

We don’t want to uninstall/reinstall the app in each of our stores and lose the inventory location/cancel fulfillment requests/move request to new location/etc. Two of the stores are fairly high volume.

-Carl

2

Hey @Carl - at the moment there’s not a way to convert a custom legacy app over to the. Dev Dash. Just sharing a prior post with some answers from one of my colleagues here:

That said, just to confirm, your main concern is having the Fulfillment settings and location assignment carry over with a reinstall? You’re right that this would be a bit tricky, and I can’t guarantee anything, but I’m happy to pass along some feedback and look into some workarounds for you if that would be helpful?

3

Hello,

Yes, our concerns revolve around the location assignment to the app and all that impacts (orders/inventory/etc). Our app handles the new auth flow fine, the newest store we added uses it, but I can’t see a safe way to migrate this with our higher volume stores.

I did run a test on one of our dev stores with a flow around

  • Make new location
  • Sync Inventory to new location (too much for sale for a bit)
  • Migrate any active orders to new location (some error for various reasons)
  • Manually fix stuck orders (this is slow and various reasons/customer service waiting/returns/etc)
  • Remove original location and inventory
  • Rename New Location to old name

And I didn’t even touch on shipping profiles that use one location vs another. This seems a very dangerous workflow, nearly impossible on our busy stores.

Open to ideas/suggestions. I can’t imagine we are the only ones with a custom app that would have these issues migrating.

Thanks

4

Hey @Carl, thanks for the detailed breakdown, I get how risky that workflow is for a busy store for sure.

One thing I can confirm is that right now, there isn’t an official migration path for converting a legacy custom app to a Dev Dashboard app. The Jan 1, 2026 change only blocked the creation of new legacy custom apps, so existing ones continue to work and their fulfillment service locations stay intact. If nothing is currently forcing you to migrate, my honest suggestion would be to just leave the legacy app in place on the high-volume stores and keep it running as-is.

Is there anything specifically driving the need to move these now, or are you trying to get ahead of a possible future deprecation? If so, my understanding is that there isn’t an imminent one, but again, I do certainly get where you’re coming from on that too just for future-proofing.

There’s no transfer mutation or tooling to carry the fulfillment service location over to a new app, since the location is bound to the app that created it. I agree that on high-volume stores this could be less than ideal and not something you’d want to attempt without a maintenance window and a very careful cutover plan.

Either way, this is legitimate feedback worth logging on our end for sure. I’ll dig into this further on my end here internally. Can’t guarantee anything in terms of a timeline, but I can log a feature request at the very least for you.

I’ll loop back once I’ve got next steps to share on my side here :slight_smile:

6

Hello @Alan_G , thanks for the detailed response.

Few reasons I/we liked the idea of migrating over here, nothing mission critical I am aware of.

  • With how things go I expect it will be deprecated fully at some point, even if its far down the line. I wanted to get moved over well before we ran into any issues with support/missing new features/random bugs that tend to happen in situations like this.
  • Even though we need a separate dev dashboard per store (Separate Shopify plans) having the data has been great. Seeing the webhook info/status/old api calls we all really appreciate seeing what was invisible before to us on custom apps.
  • There is probably a different workaround for this, but one of the guys here recently added some components that uses the Shopify CLI for the first time in our integration (previously everything was graphql orders/fulfillment/etc). This aspect is not my area at all so I could have something wrong here with him telling me he was only able to deploy on the new dev dashboard stores.

Thanks

7

Hey @Carl, thanks again for the extra context,

On the deprecation angle, I did a bit more digging on my side, and from what I can see internally there isn’t an imminent deprecation on the horizon for legacy custom apps that I’m aware of, but definitely fair instinct there.

On the CLI point, your dev is correct. Legacy custom apps don’t have an app config in the Dev Dashboard, so anything that relies on shopify app deploy (extensions, Functions, theme app extensions, web pixels, app blocks, etc) won’t work through a legacy custom app. One thing worth floating though, if you can share a bit more about what you’re looking at having deployed via the CLI, there might be a middle path. Legacy custom apps and Dev Dashboard apps can coexist on the same store, so one option would be to keep the legacy custom app running the fulfillment service (and its location) as-is, and create a separate Dev
Dashboard app just for the CLI-deployed pieces. That way you’d get the CLI workflow without having to touch the fulfillment location setup (but I realize that’s tricky and not ideal for sure)

On the migration tooling itself, I did speak with some folks on our side and they confirmed there isn’t any tooling available today for a legacy to Dev Dashboard migration specifically, and nothing on the immediate roadmap for it either. I’ve logged a feature request internally so your feedback is in front of the right folks. Can’t guarantee anything on timing, just wanted to loop back with you here to let you know this is officially logged on our end.

Let me know if I can help with anything else here - happy to clarify anything on my end.