Thanks to all for your suggestions.
Related to my sites: since one of them is more than 10k records, it will have an increase of 4 times the current cost.
My decision will be to close it.
From my point of view WIX it’s weird for future development: I cannot relieve on a company who changes policy into this way, giving me the idea that everything could happen without any limit.
Imagine that tomorrow WIX will decide to ask you to pay for each button in a website.
@loeiks yes you’re right WIX is a business brand and of course it will receive from the business what it deserves, good or bad: market rules valid for all of us.
3 Likes
Hello and thanks for your suggestions.
I’m starting studing the wix integration here
What do you suggest for the cheaper and fastest solution?
My wix subscription is moving from 400 per year to 1800 per year.
Is it worth to connect to external storage? Is it cheaper?
Thanks
I couldn’t understand what you meant about 400-1800, is your Wix premium plan changes to that to connect external DB or is it something else?
For the fastest and cheapest you can go for MongoDB which is the same technology that Wix uses for the CMS. You can use M2, M5 with very little money or M10 for around 40-65USD p/month or higher dedicated (like M10) clusters which are more expensive.
It all depends on how much traffic you have, if not a lot (lower than 3K p/month) you can even go for M0 which is free with 512mb DB storage limit. Keep in mind that when you upgrade to dedicated clusters in MongoDB you can’t revert back to non-dedicated clusters (M10> are dedicated ones)
More info here: Pricing | MongoDB
For MongoDB you can also use the library which has very similar syntax with WixData to avoid any WixData limits, when you connect an external DB your request limits for WixData will still apply. You will just avoid limits about storage, indexes etc.
To avoid all WixData (Data Platform) limits you need to use an external library.
Hey everyone!
I wanted to loop back around on this convo and share that we’ve we’ve significantly increased the CMS quotas on our Premium plans, starting today. This gives you more room to grow your clients’ sites without any added costs. 
Here are the main changes:
- For Elite and Business Elite plans, the collection item quota has been raised from 100,000 to 500,000.
- For Plus and Business plans, the collection item quota has been doubled from 10,000 to 20,000.
- For all plans, the total number of collections has increased to 1,000.
These increased quotas will be applied automatically from today, so no action is required on your part. You’ll also now be able to monitor your collection quota usage from the CMS tab in the site’s dashboard.
You can also explore the full list of changes here. If you have any questions, let me know 
Hi Loeiks, thanks for your suggestion.
I’m following it and testing it.
For now I was able to connect to mongodb based on M0.
I’m still tying to understand how to completely migrate a dataset to mongodb. For example: in case you have fields autogenerated like “record-page link” I guess I need to replicate the same logic… I’ll learn it.
Anyway the solution you provided, if I’m not wrong, goes directly by code and not by “external dataset”. Is it correct?
About the cost of my current plan… due to records number it passes from 360 eur/year to 1400 eur /year… BUT i recently discovered that wix enlarged the records count from 10.000 to 20.000 fpr the premium plan.
Thanks
Item limits are upgraded yes but to be honest it’s completely useless update for write heavy apps. Because it’s still limited by items not like 512mb limit.
You can put millions of items in 512mb. For example this would be around 100 bytes:
{
"id": 12345,
"name": "John Doe",
"age": 30,
"address": {
"street": "123 Main St",
"city": "Anytown",
"state": "CA",
"zip": "12345"
},
"email": "johndoe@example.com",
"phone": "123-456-7890"
}
And with these type of items you could create 5M+ items in your MongoDB M0 cluster. So item based limits are not useful for web application unless you are creating a basic website for a client.
The npm packages I have shrared with you is fully code it’s not related with WixData or related features like dynamic pages or visual datasets that let’s you connect data visually without code.
BUT
You can both use these type of packages with external database feature too. When you create a MongoDB database you can connect it to your website with Google Cloud (or other cloud platforms).
Then you can use it just like native Wix database with some limitations;
Your collection size, amount, index counts etc won’t be limited when you use an external collection but your requests are still limited by WixData platform. You won’t be able to use some field types like references or rich content, you won’t be able to create and manage collections visually in Wix.
So these are the details. If you don’t have any experience with JS, coding then it will be hard for you to setup and use these things and even find solutions to different database related problems you will face in the future.
My suggestion to you if you don’t have coding and database related experience;
- Try to stay in Wix included database if possible by optimizing database design.
- Try to learn MongoDB and use it with native tools like the packages I shared with you before.
There is no more option to be honest other than upgrading your Wix premium plan which is in your case a lot of money.
If you need my help to migrate from your current state to MongoDB you can message me here in forum via DM (you can do it by going to my profile page).