# Deprecation of Classic Apps begins Monday, June 30th ⚠️

**URL:** <https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082>\
**Category:** Archived Announcements\
**Created:** [March 31, 2025, 8:56pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082 "2025-03-31T20:56:45Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [May 1, 2025, 5:55pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/47 "2025-05-01T17:55:07Z")

</div>

You are partially right, but keep in mind that the apps I built 10 to 15 years ago are still working without issues. The best part is, I can move them to another platform just by copying and pasting the code. With Glide, you don’t own the code, you can’t move it elsewhere, and nearly every 3 to 6 months something gets sunset, forcing you to come back and fix it. So your comparison isn’t entirely fair, though I appreciate the effort.

---

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [May 1, 2025, 6:01pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/48 "2025-05-01T18:01:04Z")

</div>

I think I’m being misunderstood. I’m not here to complain — I moved on a long time ago. I’m here to ask for advice on how to approach my customers from Glide’s perspective. But I guess Glide is just doing what they always do.

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [May 1, 2025, 6:51pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/49 "2025-05-01T18:51:53Z")

</div>

We would recommend having your clients try the migration tool because we have found that most customers have had an easy time migrating with it. If you can get their feedback, that’d be helpful

---

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [May 1, 2025, 8:46pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/50 "2025-05-01T20:46:27Z")

</div>

The apps I built for my customers are extremely complex and rely heavily on custom CSS. They will not transition smoothly to the new Glide Apps. I would need to redo more than 50% of the layouts and spend a significant amount of time testing. No one is going to pay for that, and it’s beyond my clients’ skill level to do it themselves.

---

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [May 2, 2025, 8:32am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/51 "2025-05-02T08:32:06Z")

</div>

> [@HTML](#):
>
> I’m here to ask for advice on how to approach my customers from Glide’s perspective.

I’m not speaking for Glide. As far I understand Glide’s approach regarding Classic Apps:

1. Deprecation of Classic Apps begins Monday, June 30th. This was announced with 3 months notice. The discontinued support of Classic Apps was announced in March 2023 (2 years and 3 months notice).

2. Glide offers a migration tool that helps with migrating apps from the old platform to the new one.

Since the apps you built for your clients are complex and difficult to migrate, it seems it’s a good time for you to have earnest talks with your clients. You could explain the following:

> 1. When we built your apps, we used Glide’s now old platform. Glide discontinued support for this platform over 2 years ago, and apps that still run on the platform will be deprecated Monday, June 30th as announced late March with 3 months notice.
> 2. Your app had an amazing run, but as is it will soon not run anymore. This is how it is.
> 3. You now have a few options: decide you don’t need the app anymore and find an alternative process, rebuild the app on Glide (by yourself, with me HTML or by hiring a Glide expert), or rebuild the app outside of Glide (other nocode platform or with code). Either option will likely be inconvenient, and the two latter options will cost you either time or money. How do you feel about these options and would you like us to discuss these?

That’s it really. You’re probably going to have a few uncomfortable conversations, but it’s not your fault and that’s the world of business: there’s a subject to be discussed, you discuss and address it (or not), and move on.

You probably already are familiar with the Glide Experts directory, but just in case:

[Glide Experts Directory](https://www.glideapps.com/experts)

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [May 2, 2025, 8:38am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/52 "2025-05-02T08:38:11Z")

</div>

Just one thing I would add.

> [@HTML](#):
>
> The apps I built for my customers are extremely complex and rely heavily on custom CSS.

The use of Custom CSS was never officially supported in Classic Apps, and in fact Glide consistently warned against it and actively discouraged the use of it. Lots of us used it anyway (I did), but that was always with the understanding that we were using it at our risk and it could break at anytime without warning.

As it turned out, we got plenty of warning.

---

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [May 2, 2025, 4:52pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/53 "2025-05-02T16:52:36Z")

</div>

I did warn them not to build anything complex or critical on Glide. I offered to create a custom-coded app hosted on my own server instead. I genuinely feel bad for them, and I hope they’ll now consider moving to full-code apps, which are much easier to build today than they used to be. Thanks guys!

---

<div class="post-metadata">

**Author:** ![LVaurie](https://avatars.discourse-cdn.com/v4/letter/l/c67d28/32.png) [@LVaurie](https://community.glideapps.com/u/LVaurie)\
**Post date:** [May 7, 2025, 3:37pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/54 "2025-05-07T15:37:44Z")

</div>

I definitely need help with that.

I have a lot of classic apps deployed with custom domains.  
These Classic Apps all end with .glideapp.io

Apps are .glide.page

How can I keep the same URL?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [May 7, 2025, 3:55pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/55 "2025-05-07T15:55:33Z")

</div>

> [@LVaurie](#):
>
> deployed with custom domains.

Since you have custom domains for your apps, the Glide based url shouldn’t matter. You would be using the custom domain instead of the [glideapp.io](http://glideapp.io) or glide.page domains. Your users should be using the custom domain, so when you move the domain to the new app, it should be transparent to them. There might be a little bit of downtime while you are reconfiguring the custom domain to the new app, but probably no more than a couple of hours.

 ![1000005126](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/4/c4c942258328581ed418e1cd8cd4753571e183d7.png)

> **[Custom Domains | Glide Docs](https://www.glideapps.com/docs/reference/account/custom-domains)**
>
> Learn how to configure a custom URL for your app.

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [May 7, 2025, 6:20pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/56 "2025-05-07T18:20:14Z")

</div>

Jeff is correct!

---

<div class="post-metadata">

**Author:** ![LVaurie](https://avatars.discourse-cdn.com/v4/letter/l/c67d28/32.png) [@LVaurie](https://community.glideapps.com/u/LVaurie)\
**Post date:** [May 14, 2025, 7:51am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/57 "2025-05-14T07:51:50Z")

</div>

So, if I understand [my-name.glideapp.io](http://my-name.glideapp.io) isn’t a custom domain name? I can’t keep the same URL while migrating my app / or creating a new one to replace it?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [May 14, 2025, 7:58am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/58 "2025-05-14T07:58:25Z")

</div>

No, it’s not, and no you can’t. The domain `glideapp.io` is owned by Glide, and it only works with Classic Apps.

A custom domain is one that you own and manage. An example might be `lvaurie.com`.  
When using your own custom domain with a Glide App, it will work for both Classic and new Glide Apps. So if you assigned a custom URL to your Classic App, you could transfer that URL to your migrated App and the change would be mostly transparent to your users.

---

<div class="post-metadata">

**Author:** ![LVaurie](https://avatars.discourse-cdn.com/v4/letter/l/c67d28/32.png) [@LVaurie](https://community.glideapps.com/u/LVaurie)\
**Post date:** [May 14, 2025, 10:18am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/59 "2025-05-14T10:18:37Z")

</div>

Oh crap… 😥  
Thanks for the clear answer!

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [May 19, 2025, 7:28am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/60 "2025-05-19T07:28:43Z")

</div>

> [@Darren\_Murphy](#):
>
> A custom domain is one that you own and manage. An example might be `lvaurie.com`.  
> When using your own custom domain with a Glide App, it will work for both Classic and new Glide Apps. So if you assigned a custom URL to your Classic App, you could transfer that URL to your migrated App and the change would be mostly transparent to your users.

This is another reason we advocate for custom domains on production apps. 🙂

Clone an app, make a bunch of changes, then point the domain to the latest version.

Handy for when you’re making significant changes.

---

<div class="post-metadata">

**Author:** ![Ruben.Wills](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ruben.wills/32/17501_2.png) [@Ruben.Wills](https://community.glideapps.com/u/Ruben.Wills)\
**Post date:** [June 5, 2025, 2:58am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/61 "2025-06-05T02:58:02Z")

</div>

Hi, I’ve migrated our app and for the most part things looks OK, I’ve tried to edit the new app to make it look like the old one but I think I’m way out of my depth here, is there some option to pay someone to tidy up our migrated app to look like the old one did?.

Thanks

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [June 5, 2025, 4:23am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/62 "2025-06-05T04:23:01Z")

</div>

> **[Hire Glide Experts | Certified No Code App Developers](https://www.glideapps.com/experts)**
>
> Glide Experts are independent agencies, freelancers, and professional developers certified by Glide, ready to help make your no-code project a success. Let us match you with the perfect expert.

You can reach out to the experts here.

---

<div class="post-metadata">

**Author:** ![Kellar](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kellar/32/69515_2.png) [@Kellar](https://community.glideapps.com/u/Kellar)\
**Post date:** [June 5, 2025, 6:33pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/63 "2025-06-05T18:33:51Z")

</div>

This is the first I’ve heard of this. Does that mean I don’t have any Classic Apps?

And if not, how would I know if I have a Classic App that needs to be migrated?

Thank you,

Shawn

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [June 5, 2025, 6:37pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/64 "2025-06-05T18:37:57Z")

</div>

It will say Classic in the dashboard if it’s a classic app. It also alerts you when you go into the builder for a classic app.

 ![1000005348](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/5/550420a43e629912a3f8f79561eb47d59507fb41.png)

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [July 2, 2025, 2:53pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/65 "2025-07-02T14:53:02Z")

</div>

12 posts were split to a new topic: [Troubleshooting Comments component in migrated Classic app](https://community.glideapps.com/t/troubleshooting-comments-component-in-migrated-classic-app/82891)

---

<div class="post-metadata">

**Author:** ![ionamol](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ionamol/32/1951_2.png) [@ionamol](https://community.glideapps.com/u/ionamol)\
**Post date:** [August 10, 2025, 6:27pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/66 "2025-08-10T18:27:23Z")

</div>

Hi Glide team and community! quick help, please?

I had several **Classic Apps** under my account but I missed the migration before June 30. Now I can’t see any of those apps in my dashboard, so I also can’t run the migration tool (since there’s nothing to select).

Could you confirm:

1. Did the **automatic migration** already run for my account?

2. **Where** should the migrated apps appear and is there a way to locate them by the **original app URL/ID**?

3. If something failed, is there any way to **restore access** (even read-only) or at least retrieve:

Happy to DM whatever details you need.

Thanks in advance for pointing me to the right next steps!

[Previous page](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082.md?page=2)

[Next page](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082.md?page=4)
