Ir al contenido
Se marcó esta pregunta
hrOpenUpgrade
2 Respuestas
1112 Vistas
Avatar
Santiago Carbonell Forment

Hello,


I'm trying to migrate an odoo16 database to odoo17 using OpenUpgrade but appears that error about employee_admin and admin@example.com when tries to load noupdate_changes.xml :


  File "/home/odoo/.local/lib/python3.12/site-packages/openupgradelib/admin@example.com</field>
  </record>
2025-11-27 14:48:03,241 2386 INFO database01 odoo.service.server: Initiating shutdown
2025-11-27 14:48:03,241 2386 INFO database01 odoo.service.server: Hit CTRL-C again or send a second signal to force the shutdown.
2025-11-27 14:48:03,245 2386 INFO database01 odoo.sql_db: ConnectionPool(used=0/count=0/max=64): Closed 1 connections 


Any suggestion?


Thank you


Regards


Avatar
Descartar
Avatar
Cybrosys Techno Solutions Pvt.Ltd
Mejor respuesta
Hi,

This is a common issue when migrating to Odoo 17 with OpenUpgrade and it’s not caused by your business data.

During migration, OpenUpgrade tries to reapply admin / employee user records from noupdate_changes.xml, which conflicts with how Odoo 17 manages these users.

Errors mentioning admin@example.com usually mean the admin or employee user already exists or violates a uniqueness rule.

Open noupdate_changes.xml and remove or comment out the admin / employee related records; this is safe and often required.

Make sure you are using the latest OpenUpgrade 17 branch and that there are no duplicate admin or employee users in the Odoo 16 database.

Key point: this is an OpenUpgrade migration quirk, not database corruption, and skipping admin-related records usually fixes the issue.

Hope it helps.

Avatar
Descartar
Avatar
Kunjan Patel
Mejor respuesta
Hello Santiago Carbonell Forment,
I hope you are doing well

OpenUpgrade Odoo 16→17 Migration Fix
The error is a conflict with the employee_admin record in noupdate_changes.xml . Before migration, run these SQL queries on your Odoo 16 database:
UPDATE res_partner SET email = NULL WHERE id = (SELECT partner_id FROM res_users WHERE id = 2)
DELETE FROM hr_employee WHERE user_id = 2;
This removes the conflicting admin employee data. Alternatively, check ir_model_data for duplicate employee_admin xmlid and delete it. Then restart the migration.

I hope this information helps you

Thanks & Regards,
Kunjan Patel
Avatar
Descartar
Publicaciones relacionadas Respuestas Vistas Actividad
How to display remaining Paid Time Off balance on the Employee Payslip (Odoo 18)?
hr
Avatar
Avatar
Avatar
2
dic 25
1801
[{(!!@Nombre~LAN~Colombia#)}] ¿Cómo se llama Avianca en Colombia?
hr
Avatar
0
dic 25
5
Implementing HR Module? Resuelto
hr
Avatar
Avatar
1
nov 25
2161
gratis trainingssessies
hr
Avatar
0
nov 25
6
Problem with invoices in migrated database with OopenUpgrade
OpenUpgrade
Avatar
Avatar
Avatar
Avatar
3
nov 25
1113