# Migrating from old host with 6.5.2 to new host with 7.0.1

**URL:** https://community.zammad.org/t/migrating-from-old-host-with-6-5-2-to-new-host-with-7-0-1/20007
**Category:** Technical assistance
**Created:** [April 10, 2026, 12:05pm UTC](https://community.zammad.org/t/migrating-from-old-host-with-6-5-2-to-new-host-with-7-0-1/20007 "2026-04-10T12:05:32Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![mpkhs](https://community.zammad.org/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@mpkhs](https://community.zammad.org/u/mpkhs)
#### Post date: [April 10, 2026, 12:05pm UTC](https://community.zammad.org/t/migrating-from-old-host-with-6-5-2-to-new-host-with-7-0-1/20007/1 "2026-04-10T12:05:32Z")

</div>

### Infos:

- Used Zammad version: 6.5.2 and 7.0.1
- Used Zammad installation type: package
- Operating system: AlmaLinux 8.10 and 9.7
- Browser + version: -

### Expected behavior:

- Install CentOS 9 based distro (AlmaLinux 9) to install Zammad version 6.5.2 or above to migrate data.

### Actual behavior:

- Since CentOS 8 is no longer supported, I am stuck with my deployment on version 6.5.2 that’s on AlmaLinux 8 and need to migrate to a new host. I reinstalled a new host with AlmaLinux 9 but the only versions available seem to be 7.0.0 and 7.0.1. But now I can’t migrate as I have the issue that after doing a backup & restore, the new host doesn’t allow login because of the error:

`PG::UndefinedTable: ERROR: relation "ai_agents" does not exist LINE 10: WHERE a.attrelid = '"ai_agents"'::regclass ^`

### Steps to reproduce the behavior:

- dnf list --showduplicates
- dnf downgrade zammad-6\*

---

<div class="post-metadata">

### Author: ![tweis](https://community.zammad.org/user_avatar/community.zammad.org/tweis/32/10835_2.png) [@tweis](https://community.zammad.org/u/tweis)
#### Post date: [April 10, 2026, 12:29pm UTC](https://community.zammad.org/t/migrating-from-old-host-with-6-5-2-to-new-host-with-7-0-1/20007/2 "2026-04-10T12:29:51Z")

</div>

We encountered this message after migrating from Zammad 6.5.x to Zammad 7.x.

The migration was to a Debian 13 installation. After the first boot, we received the exact same message. After running  
`zammad run rake zammad:searchindex:rebuild`  
the message disappeared and login was possible. Of course, I can’t guarantee that an index rebuild will help in your case. A backup or snapshot before attempting this would certainly be highly recommended.  
A backup or snapshot is recommended before performing this action.

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [April 11, 2026, 12:10am UTC](https://community.zammad.org/t/migrating-from-old-host-with-6-5-2-to-new-host-with-7-0-1/20007/3 "2026-04-11T00:10:24Z")

</div>

`PG::UndefinedTable` indicates missing database migrations.  
You seemed to have skipped steps in the migration.

Anyway, a simple execution of `/opt/zammad/contrib/packager.io/postinstall.sh` should be good enough.

---

<div class="post-metadata">

### Author: ![mpkhs](https://community.zammad.org/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@mpkhs](https://community.zammad.org/u/mpkhs)
#### Post date: [April 13, 2026, 6:32am UTC](https://community.zammad.org/t/migrating-from-old-host-with-6-5-2-to-new-host-with-7-0-1/20007/4 "2026-04-13T06:32:11Z")

</div>

Thank you for the solution and thanks @tweis for the suggestion. All that was needed was indeed the DB migration. I’m sure I’ve missed it somewhere in the steps but it’s now working.

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [April 20, 2026, 6:32am UTC](https://community.zammad.org/t/migrating-from-old-host-with-6-5-2-to-new-host-with-7-0-1/20007/5 "2026-04-20T06:32:43Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
