# Advice on Moving from Google Sheets to Glide Tables

**URL:** <https://community.glideapps.com/t/advice-on-moving-from-google-sheets-to-glide-tables/56588>\
**Category:** Ask for Help\
**Created:** [January 11, 2023, 5:07pm UTC](https://community.glideapps.com/t/advice-on-moving-from-google-sheets-to-glide-tables/56588 "2023-01-11T17:07:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [January 11, 2023, 5:07pm UTC](https://community.glideapps.com/t/advice-on-moving-from-google-sheets-to-glide-tables/56588/1 "2023-01-11T17:07:11Z")

</div>

I used Google Sheets for simplicity and the ability to see data changes in a separate window in real-time (two cents worth - Glide should have their Data Editor accessible in another tab so as not to disrupt the development cycle by switching into and out of Data Editor/ Layout mode)

Unfortunately - performance with GS can be abysmal (I use working tables for all edits which usually have Computed Columns) with some updates taking 30 seconds. A quick test using Glide Tables brought this down to 1-2 seconds. Great news accept…

…I have a LOT of computed columns in almost all my edit screens (using google sheets) with LOTS of actions (and associated google tables) so this seems to ripple through the App.

I am trying to figure out how to ‘swap’ tables (same name, same layout, different underlying source (Glide instead of Google) to retain all underlying logic but I think this is a pipe dream.

My option seems to methodically migrate/rewrite each table/action/layout to use the new Glide table but I may be missing something obvious (not the first time this would have occurred with Glide dev 🙂 )

---

<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:** [January 11, 2023, 5:12pm UTC](https://community.glideapps.com/t/advice-on-moving-from-google-sheets-to-glide-tables/56588/2 "2023-01-11T17:12:25Z")

</div>

Add your vote if you haven’t already.

> [@Convert existing Sheets-based tab (data, computed columns) to Glide Table](https://community.glideapps.com/t/convert-existing-sheets-based-tab-data-computed-columns-to-glide-table/22183):
>
> Hi, As mentioned before that I started to see a good side of using Glide Tables instead of using Google Sheets in some cases, like some tables might be updated rapidly in real use. But this hunch always came a bit late; After a while of putting up so many relations & lookups & data templates, then I realized that this sheet might have less problem if I changed to Glide Table. But this means a do-over with all the table setups, not to mention all data links on the interface will be cut-off whic…

Lots of us have asked for this, so hopefully we’ll get it at some time in the not too distant future.

---

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [January 11, 2023, 5:15pm UTC](https://community.glideapps.com/t/advice-on-moving-from-google-sheets-to-glide-tables/56588/3 "2023-01-11T17:15:22Z")

</div>

I already did…just wondering if there was a fix/alternative option given all the new features/activities going on plus the push towards Pages. Something new I hoped.

Good to be back in Glide dev…I think! 😉

---

<div class="post-metadata">

**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\
**Post date:** [January 18, 2023, 5:08am UTC](https://community.glideapps.com/t/advice-on-moving-from-google-sheets-to-glide-tables/56588/4 "2023-01-18T05:08:34Z")

</div>

We are also trying to migrate to Glide Tables, however there are many concerns related to this especially with large apps, many rows.  
For example as I am testing this today on an app with only 1500 rows

- I just imported a google sheet into a blank new Glide Page, however I can’t seem to copy an entire glide column data and place it into another column.
- I cannot even delete a column. When I delete the column remains in place.

there are 2 very important features required in large apps and very easy to perform in Google Sheets. We use Glide as part of a bigger process. We collect data in it and require to move it on. So being able to delete data in Glide in order to improve our app performance is essential!

currently it seems unclear whether Glide Tables can support

- deleting thousands of rows at once. (definitely not on the editor, not sure whether if anyone tried using API)
- copying entire columns through the editor. (we want to recreate our app, use better column names to make life easier while accessing via API)

Update:  
having checked the app again now, seems like the columns actually got deleted. Quite a stressful delete though, its hard to know what to do, wait, refresh ( i did many times), delete the column again… worrying that by accident a new column would be selected and deleted… etc.

---

<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:** [January 18, 2023, 5:24am UTC](https://community.glideapps.com/t/advice-on-moving-from-google-sheets-to-glide-tables/56588/5 "2023-01-18T05:24:49Z")

</div>

> [@abdo](#):
>
> deleting thousands of rows at once. (definitely not on the editor, not sure whether if anyone tried using API)

In my experience, bulk deleting rows is best done via the API. I did some load testing late last year where I was deleting up to 100,000 rows via the API, in batches of 100. It works perfectly.

> [@abdo](#):
>
> having checked the app again now, seems like the columns actually got deleted. Quite a stressful delete though, its hard to know what to do, wait, refresh ( i did many times), delete the column again… worrying that by accident a new column would be selected and deleted… etc.

yes, that has also been my experience. Deleting a handful of rows works fine in the data editor, but once you start trying to delete hundreds or thousands of rows it becomes quite problematic.
