
task ID:2684744
closes odoo/documentation#1746 X-original-commit:825e0ede21
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
229 lines
9.0 KiB
ReStructuredText
229 lines
9.0 KiB
ReStructuredText
.. |assistance-contact| replace::
|
|
If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
|
|
our `Sales department`_.
|
|
.. _Sales department: mailto:sales@odoo.com
|
|
|
|
===
|
|
FAQ
|
|
===
|
|
|
|
.. _upgrade-faq/why:
|
|
|
|
Why upgrade
|
|
===========
|
|
|
|
* You benefit from the latest features of the :ref:`new major version
|
|
<upgrade-faq/release-notes>` released by Odoo.
|
|
* If you are in an :ref:`unsupported version <upgrade/supported-versions>`, you get a new version
|
|
with support.
|
|
|
|
.. _upgrade-faq/when:
|
|
|
|
When to upgrade
|
|
===============
|
|
|
|
Whenever you want. You can make your upgrade request as soon as a new version is released or when
|
|
your version turns unsupported, and you still wish to enjoy support.
|
|
|
|
.. _upgrade-faq/availability:
|
|
|
|
Availability of the new version
|
|
===============================
|
|
|
|
As soon as Odoo announces the release of a new major version, you can create a test upgrade request
|
|
to try the latest version. Please note that at this point, the upgrade scripts will only have been
|
|
tested with demo data. Please report any issue you might encounter while testing via the `Odoo
|
|
Support page <https://www.odoo.com/help>`_ and make sure to be happy with your test version before
|
|
requesting the upgrade of your database in production.
|
|
|
|
.. _upgrade-faq/duration:
|
|
|
|
Duration of the upgrade
|
|
=======================
|
|
|
|
It is impossible to give time estimates for every upgrade request.
|
|
|
|
In general, the "smaller" the database, the quickest the upgrade request is completed. A single-user
|
|
database that uses only CRM will be processed faster than a multi-company, multi-user database that
|
|
uses Accounting, Sales, Purchase, and Manufacturing.
|
|
|
|
You can expect the time it takes for the platform to upgrade the test database to be similar to the
|
|
production upgrade.
|
|
|
|
.. _upgrade-faq/project:
|
|
|
|
Duration of the upgrade project
|
|
-------------------------------
|
|
|
|
It depends on the user involvement (the time spent on testing, reporting problems, etc.) and the
|
|
issues encountered that might need to be addressed by our technical team.
|
|
|
|
So, in a nutshell, what can impact your upgrade lead time?
|
|
|
|
* Source & targeted versions
|
|
* Installed apps
|
|
* Volume of data
|
|
* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
|
|
* Installation of new apps or configuration changes after the start of the test phase
|
|
* User commitment
|
|
|
|
.. _upgrade-faq/custom-modules:
|
|
|
|
Upgrade of the custom modules
|
|
=============================
|
|
|
|
As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional
|
|
service is subject to additional fees.
|
|
|
|
Depending on your situation, the custom code could be upgraded by our services, by one of our
|
|
partners, or you can do it yourself.
|
|
|
|
.. note:: |assistance-contact|
|
|
|
|
.. _upgrade-faq/upgrade-or-migration:
|
|
|
|
Upgrade or Migration
|
|
====================
|
|
|
|
An upgrade is switching to a newer version of Odoo, while a migration reflects the change of
|
|
:ref:`editions <upgrade-faq/editions-change>` or change of :ref:`hosting type
|
|
<upgrade-faq/hosting-types-switch>`.
|
|
|
|
.. note:: |assistance-contact|
|
|
|
|
.. _upgrade-faq/editions-change:
|
|
|
|
Editions change (from Community to Enterprise)
|
|
==============================================
|
|
|
|
The upgrade always returns an Enterprise edition of Odoo, whether the database you sent was a
|
|
community or enterprise edition. It is required to have an enterprise subscription to upgrade.
|
|
|
|
.. note::
|
|
If you need assistance on this matter, please contact us via the `Odoo Support page
|
|
<https://www.odoo.com/help>`_.
|
|
|
|
.. seealso::
|
|
- `Editions <https://www.odoo.com/page/editions>`_
|
|
|
|
.. _upgrade-faq/hosting-types-switch:
|
|
|
|
Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. Cloud Platform - Odoo.sh)
|
|
=================================================================================================
|
|
|
|
An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
|
|
|
|
Open the following link to get :doc:`more information about how to change your hosting type
|
|
<../maintain/hosting_changes>`.
|
|
|
|
.. note:: |assistance-contact|
|
|
|
|
.. _upgrade-faq/upgrade-report:
|
|
|
|
The Upgrade Report
|
|
==================
|
|
|
|
When an upgrade request completes successfully (test or production), you receive an email
|
|
notification about it that includes an 'Upgrade Report'. This report is also sent to you via the
|
|
Discuss app. It contains valuable information regarding changes that occurred during the upgrade.
|
|
While it serves as a guide to possible issues to look out for, it is not an exhaustive list. It
|
|
remains imperative that you test the upgraded database thoroughly and report any discrepancies you
|
|
might find, before you decide to upgrade your production database.
|
|
|
|
.. _upgrade-faq/custom-views:
|
|
|
|
Custom views
|
|
============
|
|
|
|
During the upgrade, some custom views might get disabled for technical reasons. Therefore they might
|
|
have to be fixed after the upgrade. The :ref:`Upgrade Report <upgrade-faq/upgrade-report>` that is
|
|
generated after the upgrade is available in the Discuss app, and lists all the custom views that
|
|
might be impacted by this.
|
|
|
|
.. _upgrade-faq/release-notes:
|
|
|
|
Release Notes by version
|
|
========================
|
|
|
|
Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
|
|
features and improvements made in each version.
|
|
|
|
How long is my test available for
|
|
=================================
|
|
|
|
An Odoo Online (SaaS) test database is available for one month by default. We can extend this trial
|
|
period upon request. For Odoo.sh or on-premise, there is no restriction.
|
|
|
|
How many tests to perform before upgrading to production?
|
|
=========================================================
|
|
|
|
As many as needed. When you are comfortable with the database, run a last test upgrade 48 hours
|
|
before requesting your production upgrade and test your workflows one last time.
|
|
|
|
How to/Where to report upgrade issues?
|
|
======================================
|
|
|
|
If you encounter issues during the upgrade process, please contact the Odoo Support through the
|
|
`Odoo Support page <https://www.odoo.com/help>`_.
|
|
|
|
- To report an issue discovered during the testing phase, please select **An issue related to my
|
|
upgrade (test phase)**.
|
|
- To report an issue discovered post-upgrade, please select **An issue related to my upgrade
|
|
(production)**.
|
|
|
|
Upgrading to production
|
|
=======================
|
|
|
|
Once you have completed testing and are happy with the result, you decide on a date and time when
|
|
you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the
|
|
production upgrade.
|
|
|
|
How is my data handled in the Upgrade Platform?
|
|
===============================================
|
|
|
|
The Odoo Upgrade platform uses the same Privacy Policy as the rest of Odoo.com services.
|
|
|
|
Your data is hosted on servers that follow our security guidelines, namely:
|
|
|
|
- SSL - All web connections to client instances are protected with 256-bit SSL encryption
|
|
(HTTPS with a 2048-bit modulus SSL certificate), and running behind Grade A SSL stacks. All our
|
|
certificate chains are using SHA-2 already.
|
|
- Safe System - Our servers are running recent Linux distribution with up-to-date security patches,
|
|
with firewall and intrusion countermeasures (not disclosed for obvious reasons).
|
|
|
|
Servers are located at the same locations as our Cloud providers with the following services:
|
|
|
|
- Restricted perimeter, physically accessed by authorized data center employees only
|
|
- Physical access control with security badges or biometrical security
|
|
- Security cameras monitoring the data center locations 24/7
|
|
- Security personnel on-site 24/7
|
|
|
|
The uploaded and migrated databases uploaded to the Upgrade platform are kept for up to 3 months and
|
|
are permanently deleted following that period.
|
|
|
|
You can learn more about privacy and data handling at Odoo by visiting our `General Data Protection
|
|
Regulation page <https://www.odoo.com/gdpr>`_.
|
|
|
|
Rolling Release (applicable to Odoo Online databases)
|
|
=====================================================
|
|
|
|
This feature allows customers to upgrade their database directly from a message prompt sent to the
|
|
database administrator as soon as the new version is released. Odoo first tests the upgrade to the
|
|
next version. The rolling release upgrade option is displayed if the automated tests are successful.
|
|
The message offers two options:
|
|
|
|
#. To 'Upgrade Now', which immediately triggers the upgrade of your live production database.
|
|
|
|
#. To take you to your `database manager <https://www.odoo.com/my/databases/>`_ where you can
|
|
`request an upgraded test database <https://upgrade.odoo.com/#online/>`_ and check the upgraded
|
|
test database for any discrepancies.
|
|
|
|
When you choose to proceed with the production upgrade directly, make sure all users have saved
|
|
their work and are logged out. The upgrade takes approximately 15 minutes. During this time your
|
|
database is unreachable. If you notice any problem after the upgrade, please report it via the `Odoo
|
|
Support page <https://www.odoo.com/help>`_.
|
|
|
|
.. note::
|
|
If you are using the Website or Studio app, we recommend you always do a test upgrade before
|
|
upgrading your production instance.
|