As I hope everyone is aware, the legacy plan changeover is happening on 1st October so this is the last month before that happens. I am a little concerned with the lack of communication from Bubble regarding this.
I have seen before that people who have changed over to new pricing mid month have got messages that the WUs from that month will count towards that total (seems really stupid to count something that wasn’t part of the plan at the time!).
I’m sure there are a few others like me who are still doing some optimizations and testing some things out as we get closer to the deadline so I was curious how the changeover is actually going to happen in practice as I don’t want to be optimizing for September to then be charged for all those WUs if I do changeover prior to being ready.
What happens to Bubble plans on Legacy if they don’t change and let the natural changeover happen? I would hope that Bubble would have something in the dashboard that we can select the plan that we will go onto. Is this something that is being worked on?
Will there actually be a wider communication / understanding of how this roll out is happening? I am pretty sure I am not the only one still on legacy but that may be the case!
Is the 1st October deadline actually going to change everyone over or will those with renewal dates after this be fine up until the renewal date and then have to change from the renewal?
Would be helpful to understand all of this a bit more as I am sure there are others who have these questions other than just me. Ideally what I’d love to see is something in the dashboard saying it is happening (which we know) and to pre-choose the plan that we intend to go on if we didn’t switch prior to the changeover happening.
I hope to see something like this as the thought of paying for WUs whilst on a legacy plan makes no sense if changing mid month and judging by all the other threads with trying to understand how WUs are actually calculated, you can’t blame someone for wanting to leave it as late as possible - Bubble simply haven’t made it appealing to do it prior.
Surely just by selecting the plan? @fede.bubble the issue that means you’re charged for current month’s WU when migrating needs to be sorted out - if a user migrates on Sept 20, they’re charged for all of September’s WU even though contractually they’ve been on legacy for those first 20 days. It’s not a good look for Bubble when people migrating will already be annoyed if their prices increase
agree the main issue is this botched rollout with charging WUs for a time when you aren’t on a WU plan. If there was confirmation that this isn’t happening now until the time then it would make it a simpler thing for us to just know the deadline and do the moveover prior but alas we still need time this month to ensure we are 100% ready for the changeover and I’m sure we’re not the only ones.
I mentioned this a few months back when they announced they were doing the migration…I believe Bubble has it sorted in that, we are migrated on our renewal date as you’ve indicated in this thread…that means, nobody would be charged for previous WUs, because the situation in which a user is charged for WUs from earlier in their billing period is when they migrated before the end of the current period.
For example, your current period billing is August 12 - September 11 and you migrated on September 1, Bubble would charge for the WUs from August 12 - September 1…so for a user in this situation, I believe Bubbles approach is to migrate automatically on September 11, which should result in no charges fro WUs from earlier in the period.
My money is they understand the costs of having to fix the issue in retrospect with lots of dissatisfied customers is greater than ensuring pre-emptively that there will be no cases like this from their planned migration.
I’m not certain that this is true, unless there’s evidence here/somewhere of Bubble saying the contrary. When migrating, historically, you’ve been charged for all WU in the calendar month (because for some silly reason, WU is synced with the calendar month rather than the app billing cycle) and I haven’t seen anywhere that it’s change.
The email also indicates that regardless of billing cycle, monthly plan apps will migrate on October 1st (perhaps to avoid incurring WU charges for the previous month).
That said, I read just about everything Bubble puts out, so if I don’t understand how a migration is charged then someone that gets that email after 18 months without even logging into the Bubble editor will have no clue!
Plan: Apps on legacy monthly plans will be automatically migrated based on this logic: Personal will migrate to Starter, Professional to Growth, and Production to Team. If you decide to change to a different workload-based plan after the auto-migration, Bubble automatically prorates the difference in cost as a credit, which either immediately applies to the cost of a more expensive plan or remains as a credit balance in your account. Apps on legacy annual plans will be automatically migrated on their renewal date.
Workload add-ons: Workload overages will automatically be enabled in case your app needs more workload than what’s included in your plan, but you can disable overages after the auto-migration. Additionally, your app will not be automatically subscribed a workload tier, but you can use the subscription planner to see if a workload subscription makes sense for your usage.
Yes, we will continue to send reminder emails this month. We also added in-product reminders, including a pop-up that appears every week and a banner that will appear all month.
Can you let us know what other questions you have about the rolllout and we’ll make sure to address them.
The Oct 1 deadline is only applicable for apps on monthly plans. Apps on annual plans will be migrated on the renewal date of their annual plan.
When you switch from a Legacy plan to a new Workload-based plan, you will be charged for all previous Workload Unit (WU) usage for the current calendar month. This means that even after downgrading, any workload that was used while on the legacy plan during the current month will be billed.
In this case, I would recommend waiting until October 1st to switch to a new pricing plan. Workload units are calculated based on the calendar month, not your billing cycle, so that would ensure you are not charged for any workload units accrued in the month of September.
Hey all, adding more here.
The team implemented a change so that a user migrating from a legacy plan to a new workload-based plan in the middle of the month will not count any workload accrued before the time of migration in that month.
(This logic also applies to any apps on annual legacy plans after October 1, when that plan auto-migrates over to a new plan on the date the annual subscription renews).
Hopefully this eases some of the stress points raised about when legacy users should be migrating and why.
