Public Access
fix(copy): qualify version upgrades as in-version only; major migration is a separate quote
The four 'version upgrades are run for you' lines (black-friday, hosting-offers, hosting-2027 body + table row, llms.txt) and their JSON-LD descriptions now say updates and in-version upgrades are included, and name a major-version migration as a separate, quoted service. terms.html: migration = separate service, quoted separately; release list no longer reads stale (names Odoo 20 as current). No offer, price, page structure or ad change.
This commit is contained in:
1 parent
ef0ea506c2
commit
46b943bffe
5 files changed
+14
-12
No files matched your search
+1
-1
@@ -163,7 +163,7 @@
|
||||
|
||||
<div class="legal-card">
|
||||
<h2>Version upgrades and migrations</h2>
|
||||
<p>Ask our support team for a version upgrade. We migrate databases on the main Odoo releases 17, 18 and 19. We do not support patch releases such as 18.1.</p>
|
||||
<p>Updates and upgrades within your current Odoo version are included in your plan. Moving a database to a new major Odoo version is a migration: it is a separate service and is quoted separately, so ask our support team for a quote. Our migration service covers databases on the main Odoo releases 17, 18 and 19. New instances can run Odoo 20, the current release. We do not support patch releases such as 18.1.</p>
|
||||
</div>
|
||||
|
||||
<div class="legal-card">
|
||||
|
||||
Reference in new issue
Block a user