# Mautic upgrade to 4.4.10 -\> 5.0.1 breaks

**URL:** <https://forum.mautic.org/t/mautic-upgrade-to-4-4-10-5-0-1-breaks/30440>\
**Category:** Mautic 5 Install/Upgrade Support\
**Created:** [January 11, 2024, 5:16am UTC](https://forum.mautic.org/t/mautic-upgrade-to-4-4-10-5-0-1-breaks/30440 "2024-01-11T05:16:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [January 11, 2024, 9:23am UTC](https://forum.mautic.org/t/mautic-upgrade-to-4-4-10-5-0-1-breaks/30440/2 "2024-01-11T09:23:59Z")

</div>

Hi there,

Thanks for reporting the issue and sharing the detailed logs.

We have the point groups migration problem already reported and a fix proposed, which I found by searching for the error you have in the logs 🙂 .

Here’s the post:

> [@How to update 5 to 5.0.1 via composer?](https://forum.mautic.org/t/how-to-update-5-to-5-0-1-via-composer/30430/7):
>
> There is an open GH issue for this: Please follow the discussion and join in with new inputs.

Here is the fix for it which was shared late yesterday, hopefully it will be released imminently:

> <https://github.com/mautic/mautic/pull/13195>
>
> \<!-- ## Which branch should I use for my PR?
> 
> Assuming that:
> 
> a = current ma…jor release
> b = current minor release
> c = future major release
> 
> \* a.x for any features and enhancements (e.g. 5.x)
> \* a.b for any bug fixes (e.g. 4.4, 5.1)
> \* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) --\>
> 
> | Q | A
> | -------------------------------------- | ---
> | Bug fix? (use the a.b branch) | \[Y \]
> | New feature/enhancement? (use the a.x branch) | \[N \]
> | Deprecations? | \[N \]
> | BC breaks? (use the c.x branch) | \[\]
> | Automated tests included? | \[\] 
> | Related user documentation PR URL | mautic/mautic-documentation#... 
> | Related developer documentation PR URL | mautic/developer-documentation#... 
> | Issue(s) addressed | Fixes #12993 
> 
> \<!--
> Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
> - Always add tests and ensure they pass.
> - Bug fixes must be submitted against the lowest maintained branch where they apply
> (lowest branches are regularly merged to upper ones so they get the fixes too.)
> - Features and deprecations must be submitted against the "4.x" branch.
> \--\>
> 
> \#### Description:
> This PR fixes the issue with point groups migration
> \<!--
> Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
> \--\>
> 
> \#### Steps to test this PR:
> 
> \<!--
> This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
> \--\>
> 1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs \[here\](https://contribute.mautic.org/contributing-to-mautic/tester))
> 2. Run \`ddev exec php bin/console doctrine:migrations:migrate\`
> 
> \<!--
> If you have any deprecations, list them here along with the new alternative.
> If you have any backwards compatibility breaks, list them here.
> \--\>

Please test it and report back if this resolved the issue on the GitHub pull request - I posted instructions here: [Unable to pass DB migrations: Table 'point\_groups' already exists · Issue #12993 · mautic/mautic · GitHub](https://github.com/mautic/mautic/issues/12993#issuecomment-1885291503) on how to leave a report.

---

_[View the full topic](https://forum.mautic.org/t/mautic-upgrade-to-4-4-10-5-0-1-breaks/30440)._