# Convert glide table to big table **URL:** \ **Category:** Ask for Help\ **Created:** [August 3, 2023, 6:36am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651 "2023-08-03T06:36:06Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Ovi](https://avatars.discourse-cdn.com/v4/letter/o/3ab097/32.png) [@Ovi](https://community.glideapps.com/u/Ovi)\ **Post date:** [August 3, 2023, 6:36am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/1 "2023-08-03T06:36:06Z")
Is there a way to convert a glide table to a glide big table ? ---
**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:** [August 3, 2023, 6:39am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/2 "2023-08-03T06:39:02Z")
No, not directly. The closest you can get would be to export/import the non computed data. Given the limitations of Big Tables, I think that it’s unlikely that we’ll see a direct conversion tool any time soon. ---
**Author:** ![Ovi](https://avatars.discourse-cdn.com/v4/letter/o/3ab097/32.png) [@Ovi](https://community.glideapps.com/u/Ovi)\ **Post date:** [August 3, 2023, 6:39am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/3 "2023-08-03T06:39:46Z")
@Darren_Murphy what are the limitations of Big tables ? ---
**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:** [August 3, 2023, 6:44am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/4 "2023-08-03T06:44:22Z")
> **[Big Tables](https://www.glideapps.com/docs/essentials/data-sources/big-tables)** > > Scale your app with up to 10 million rows of data. (refer to the “Limitations of Big Tables” sub-section) ---
**Author:** ![Ovi](https://avatars.discourse-cdn.com/v4/letter/o/3ab097/32.png) [@Ovi](https://community.glideapps.com/u/Ovi)\ **Post date:** [August 3, 2023, 6:56am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/5 "2023-08-03T06:56:52Z")
@Darren_Murphy the limitation of glide tables is 25000 rows per table or per app ? ---
**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:** [August 3, 2023, 7:04am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/6 "2023-08-03T07:04:09Z")
The limit is per App, and depends on your plan. It starts at 100k (not 25k) for Business, and goes up from there. This is all broken down on the [Pricing Page](https://www.glideapps.com/pricing). ---
**Author:** ![Ovi](https://avatars.discourse-cdn.com/v4/letter/o/3ab097/32.png) [@Ovi](https://community.glideapps.com/u/Ovi)\ **Post date:** [August 3, 2023, 10:29am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/7 "2023-08-03T10:29:30Z")
@Darren_Murphy let’s take the case when I create multiple apps on the pro plan and then I need to scale the apps … how can this be achieved, when the apps are created using Glide normal tables ? From my point of view , I need to recreate the apps using another type of table … am I right ? ---
**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:** [August 3, 2023, 11:21am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/8 "2023-08-03T11:21:17Z")
You won’t necessarily need to re-build the whole App. You just need to do a bit of forward planning. Identify those tables that you expect will need to be migrated to Big Tables, and treat them as if they are Big Tables from day one. That is: - minimise your use of computed columns in those tables. - where you do use computed columns, try not to add any that would not be supported if they were Big Tables. This applies to the tables themselves, as well as other tables that reference them. If you take that approach, you’ll find it much easier to migrate them to Big Tables when the time comes. ---
**Author:** ![burningmikey](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/burningmikey/32/49706_2.png) [@burningmikey](https://community.glideapps.com/u/burningmikey)\ **Post date:** [August 3, 2023, 2:33pm UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/9 "2023-08-03T14:33:52Z")
As we cannot target big table computed columns with relations, is it fair to say that starting day one with normal tables, we could favor relations to raw columns and then compute lookups with JavaScript columns? ---
**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:** [August 4, 2023, 1:08am UTC](https://community.glideapps.com/t/convert-glide-table-to-big-table/64651/10 "2023-08-04T01:08:16Z")
> [@burningmikey](#): > > we could favor relations to raw columns and then compute lookups with JavaScript columns? Basically try any means you can to work with basic/raw columns, including setting computed column values to a normal column, which is my go-to method these days. Then you can work with the basic/raw values.