跳至内容
Odoo 菜单
  • 登录
  • 免费试用
  • 应用程序
    财务
    • 会计
    • 发票
    • 费用
    • 电子表格 (BI)
    • 文档
    • 电子签名
    销售
    • 客户关系管理
    • 销售
    • POS 销售点管理-零售
    • POS 销售点管理 - 餐厅
    • 订阅
    • 租赁
    网站
    • 网站设计
    • 电子商务
    • 博客
    • 论坛
    • 在线客服
    • 在线学习
    供应链
    • 库存
    • 制造
    • 产品生命周期
    • 采购
    • 维护保养
    • 品控
    人力资源
    • 员工
    • 招聘
    • 休假
    • 评价
    • 内部推荐
    • 车队
    营销
    • 社媒营销
    • 电邮营销
    • 短信营销
    • 近期活动
    • 营销自动化
    • 网上调查
    服务
    • 项目管理
    • 工时单
    • 现场服务
    • 服务台
    • 排期
    • 预约
    生产力
    • 讨论
    • 批核
    • IoT物联网
    • VoIP
    • 知识库
    • WhatsApp
    第三方应用软件 Odoo 定制 Odoo云端平台
  • 行业
    零售
    • 书店
    • 服装店
    • 家具店
    • 食品杂货店
    • 五金店
    • 玩具店
    餐饮与酒店服务
    • 酒吧及酒馆
    • 餐厅
    • 快餐
    • 民宿
    • 饮品分销商
    • 酒店
    房地产
    • 房地产代理
    • 建筑师事务所
    • 建造业
    • 地产管理
    • 园艺
    • 业主协会
    咨询
    • 会计师事务所
    • Odoo合作伙伴
    • 市场推广公司
    • 律师事务所
    • 人才招聘
    • 审核 & 认证
    制造
    • 纺织
    • 金属
    • 家具
    • 食品
    • 啤酒厂
    • 企业礼品
    保健与健身
    • 体育俱乐部
    • 眼镜店
    • 健身中心
    • 健康从业者
    • 药房
    • 发型屋
    商贸服务
    • 维修人员
    • IT 硬件及支持
    • 太阳能系统
    • 鞋匠
    • 清洁服务
    • 暖通空调服务
    其他
    • 非营利组织
    • 环境机构
    • 广告牌租赁
    • 摄影服务
    • 自行车租赁
    • 软件经销商
    浏览所有行业
  • 社区
    学习
    • 教学视频
    • 文档
    • 认证
    • 培训
    • 博客
    • 播客
    赋能教育
    • 教育计划
    • Scale Up! 商业游戏
    • 参观Odoo
    获取软件
    • 下载
    • 版本对比
    • 发布
    合作
    • Github
    • 论坛
    • 近期活动
    • 翻译
    • 成为合作伙伴
    • 合作伙伴服务
    • 注册您的会计事务所
    获取服务
    • 寻找合作伙伴
    • 查找会计服务
    • 预约顾问咨询
    • 安装及推行服务
    • 客户参考
    • 支持
    • 升级
    Github Youtube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    获取演示
  • 定价
  • 技术支持

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

  • 客户关系管理
  • e-Commerce
  • 会计
  • 库存
  • PoS
  • 项目
  • MRP
All apps
只限注册用戶才可与社群互动。
所有帖文 人 徽章
标签 (查看所有)
odoo accounting v14 pos v15
关于此论坛区
只限注册用戶才可与社群互动。
所有帖文 人 徽章
标签 (查看所有)
odoo accounting v14 pos v15
关于此论坛区
帮助

Discussion on Data Migration Methods

订阅

此帖文有活动时,接收通知

此问题已终结
migrationdatamigrationv15v18
2 回复
775 查看
形象
RGonzalez

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.

0
形象
丢弃
Creyox Technologies

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

RGonzalez
编写者

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.

形象
Cybrosys Techno Solutions Pvt.Ltd
最佳答案

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

0
形象
丢弃
形象
Ray Carnes (ray)
最佳答案

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 
0
形象
丢弃
RGonzalez
编写者

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.

Ray Carnes (ray)

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

喜欢讨论吗?不要只阅读,加入进来!

立即创建账户,享受专属功能,与我们的精彩社区互动!

注册
相关帖文 回复 查看 活动
Odoo Community 15 to 17 migration procedure ? 已解决
migration v15 v17
形象
形象
形象
形象
形象
5
6月 25
19725
How to migrate Odoo 14 DB to Odoo 15 DB 已解决
migration odoo v15
形象
形象
1
1月 23
14247
Module migratior error 已解决
migration v14 v15
形象
形象
形象
3
9月 22
4985
How to migrate custom addons from odoo12 to odoo15 from odoo.sh with existing data?
migration odoo12 v15
形象
0
7月 22
3191
Migration from bitrix24 CRM to Odoo
crm migration v15
形象
形象
形象
2
11月 23
5346
社区
  • 教学视频
  • 文档
  • 论坛
开源
  • 下载
  • Github
  • Runbot
  • 翻译
服务
  • Odoo.sh 托管
  • 支持
  • 升级
  • 自定义开发服务
  • 教育
  • 查找会计服务
  • 寻找合作伙伴
  • 成为合作伙伴
关于我们
  • 我们的公司
  • 品牌资产
  • 联系我们
  • 招聘
  • 近期活动
  • 播客
  • 博客
  • 客户
  • 法律 • 隐私
  • 安全
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk slovenščina Español (América Latina) Español ภาษาไทย Türkçe українська Tiếng Việt

Odoo致力于为企业管理提供高效智能的开源解决方案,是全球业内高速成长的软件服务商之一,逾七百五十万用户选择Odoo进行数字化升级。通过一系列全业务链覆盖、高度集成、简单易用的商业应用,助力企业实现信息化改革、降本增效并释放公司增长潜力。

Odoo独特的价值在于是一款非常容易使用又完全集成的应用。

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now