So, I have tested adding columns with the WKT format into Carto, and it has always worked great (I tried 1 row, then 1000 random rows from our data). I geocoded it on load by naming the column with the WKT the_geom. When I uploaded all the data, some of the data was corrupted (random numbers and letters, no format). After testing, I have found the following:
The csv being used is normal and fine.
When the data is mixed (some the_geom values are blank, some are in WKT format), less than 40,000 rows can be added (40K doesn't work, 39.5K does)
The data that is corrupted is the first 24,000-25,000 rows (it varies) that have a value in the_geom column (only those first ones, no matter whether its 40K rows or 1.1 million).
If I upload 39K rows, the same rows that were corrupted before are now fine and geocoded.
I can load as many rows as I want, as long as the_geom is in WKT format OR blank, but not mixed.
All of this to say, I found a work around (upload 2 separate tables [one with the_geom WKT format, the other blank], then using sql union to combine them). Unfortunately, I cannot make a table out of these 2 because I have reached the size limits for our account (Xentity). Any ideas what is causing this? If not, is there any way we could do a one time extension of the DB size, in order to combine the tables (then delete the 2 halves)?