Перейти к содержимому
Odoo Меню

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

  • CRM
  • e-Commerce
  • Бухгалтерия
  • Склад
  • PoS
  • Проекты
  • MRP
All apps
Чтобы взаимодействовать с сообществом, необходимо зарегистрироваться.
Этот вопрос был отмечен
2 Ответы
339 Представления

Hello everyone, I hope you're all doing well.


I have an interesting requirement to discuss. I'm trying to migrate data from V15 to V18. The main problem is that the company that sold us V15 no longer exists, so I don't have the updated code for V18, which prevents me from using the Odoo.sh update process.


With this in mind, I only have the following options left:

1. Pay for a perpetual V15 subscription for local or web use, maintaining data persistence.

2. Perform a schema-to-schema mapping to migrate all the information.

3. Manually upload all the data to the system using CSV and UI, setting computed data as editable to facilitate the loading of auto-generated data (sequences, amounts, etc.).


Each option has its advantages and disadvantages, both objectively and subjectively.


1. Subscription Payment.

The company doesn't want to pay an extra membership fee just to maintain persistence. I tried a local installation, but the community version is obviously not compatible with our enterprise version, and this version requires a license.


2. Schema-to-Schema Mapping.

This is a considerably lengthy and extremely methodical task, especially if data integrity is to be maintained. For our database, this would involve validating a total of 200 tables for mapping, with any number of columns. After this, migration scripts would need to be created for each model, although this is easier with AI.


3. Manual Loading.

This, like the previous option, is considerably lengthy, but more mechanical than methodical. It would involve a total of two years' worth of data, and would only require manually setting up financial and inventory transaction data, since data such as customers, products, opportunities, quotes, and tickets can be easily handled via a script. In total, this would involve approximately 3,000 accounting entries. The good thing is that we could use an RPA to handle the setup record by record. The complexity lies in the computerized data; doing things manually could cause problems if the procedure isn't followed in the order it was executed. A practical example of this would be inventory operations, where the receipt date field is automatically assigned the current date.

I've been thinking a lot about which of the last two options would be the most practical for a migration with a 3- to 4-month timeframe, and I'd love to have more perspectives to determine an option, or a new alternative.


Thank you in advance. Have a great weekend.

Аватар
Отменить

Hello,

Do you have access to your current Odoo.sh instance? How much customization have you implemented in v15?

Let us know, and we'll do our best to help you migrate to v18 with your existing data, without any unnecessary steps.

Thanks,
info@creyox.com

Автор

Hello, I hope you are well.


Thank you very much for your prompt response.


We have several customizations, practically the entire localization; however, we have developed our own localization and what we want is to migrate from one version to another using this new data schema as our target.

Лучший ответ

Hi,


Migrating from Odoo 15 Enterprise to Odoo 18 without access to the original vendor’s code or Odoo.sh repository is indeed complex, especially since the enterprise version requires a valid license and code compatibility. Of the three options you’ve outlined, each has trade-offs depending on your priorities, cost, accuracy, and time.


Maintaining a perpetual subscription is the easiest way to preserve data integrity and ensure legal access to the codebase, but if the company refuses to pay, it’s not a viable path. The schema-to-schema migration (option 2) is the most technically accurate approach since it preserves relationships and dependencies across tables, but it demands deep database knowledge and time to validate all models. It’s best suited if data consistency and accounting traceability are top priorities.


The manual loading option (option 3) is more practical if you can tolerate some data loss in non-critical areas and rely mainly on high-level historical data (e.g., balances, inventory valuations, or sales summaries). Using RPA scripts or import templates could make this feasible within your 3–4 month timeframe, though care is needed with computed fields and transaction order.


In short, if your goal is accuracy and continuity, go with schema mapping and scripts; if you prioritize speed and simplicity, opt for manual imports with automation support. A hybrid approach, automating imports for master data and scripting key financial and stock movements,often offers the best balance for migrations like this.


Hope it helps

Аватар
Отменить
Лучший ответ

You have several options:

1 - IDEAL / NO WORK AT ALL

It may be possible to keep a single read only license to your old system

  • Pros - easy to look things up, nothing new to learn
  • Cons - it is another system, so now things are in two places

2 - QUICKEST / EASIEST

Import Excel sheets of the relevant information into Odoo Spreadsheets via the Documents App

  • Pros - get access to what you need without much work to import
  • Cons - harder to search for things, not integrated well

3 - MORE WORK

Create a Studio App and import tables of CSV data

  • Pros - can use Odoo filtering and search, form and list and kanban views, can link to Customers via Smart buttons
  • Cons - takes more time

4 - EVEN MORE WORK

Import Monthly Trial Balances

  • Pros - you can run year on year comparisons
  • Cons - takes even more time

5 - THE MOST WORK

Import Transactions

  • Pros - works as if you were using Odoo the whole time
  • Cons - VERY VERY VERY time consuming, needs scripts, very advanced knowledge required, may not have a good return on investment
Аватар
Отменить
Автор

Hello, I hope you are well.

Thank you very much for your quick response.

I hadn't considered the idea of ​​having a single-user license, and it's not expensive at all, around 160ドル per year with all the applications.

Now, I'm wondering where to get the Enterprise version code to perform a local installation, because I've searched the official Odoo website, and it only shows up to version 16, and the GitHub link for Enterprise isn't working. And since the Community version doesn't have the Studio app, it will conflict with my database dump.

I was told this weekend that there's a page for Odoo partners where you can access the Enterprise version code.

I appreciate your previous help, and if you could help me with this last question, I would be very grateful.

Anyone with a valid subscription can download Odoo Enterprise from odoo.com/download

Не оставайтесь в стороне – присоединяйтесь к обсуждению!

Создайте аккаунт сегодня, чтобы получить доступ к эксклюзивным функциям и стать частью нашего замечательного сообщества!

Регистрация
Похожие посты Ответы Просмотры Активность
5
июн. 25
18753
1
янв. 23
14038
3
сент. 22
4792
0
июл. 22
3024
2
нояб. 23
5159

AltStyle によって変換されたページ (->オリジナル) /