upgrading 8.4.2 to 9+ DB only

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jamie
    Junior Member
    • Aug 2025
    • 4

    #1

    upgrading 8.4.2 to 9+ DB only

    Hello all,

    i am trying to upgrade a much loved (used) install to 9+ but it is continuously having errors in weird places that i cant fix and i am starting to think it i'd be better off just trashing the current install putting a new 9.1 version up and changing the DB

    has any one tried this? any one know if its even possible?

    it looks like a great tool but i am far more used to composer upgrades than this custom script that doesn't give much feedback as to what or where the problem is

    thanks
    Jamie

  • jamie
    Junior Member
    • Aug 2025
    • 4

    #2
    the ai he tells me to just overwrite the current files Use the official pre-packaged EspoCRM-9.0.8.zip from GitHub, unzip it over your install, and then run the upgrade script. and run the script but that doesn't seem to be working

    Comment

    • yuri
      EspoCRM product developer
      • Mar 2014
      • 9225

      #3
      Would be helpful if you share some of your errors.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment

      • jamie
        Junior Member
        • Aug 2025
        • 4

        #4
        Thanks for your response.

        It looks like our installation may have deeper issues than expected — we're missing key files like composer.json and the tests/ directory, which I understand have been in the repo for years.

        Our original setup (from Dec 2021) was based on the ZIP file from your site, and it seems the latest ZIPs still exclude these files, which has left me quite confused. I’ve also run into errors about missing vendor files when trying to run the upgrade script — though it seems more than just vendor content is missing.

        I've disabled all extensions I can (some are throwing errors), and coming from a Laravel background, I'm still adjusting to the upgrade process in EspoCRM.

        At this point, I believe a fresh install of 9.1 is the best path forward — we just need to ensure all our existing data is preserved.

        Any guidance would be greatly appreciated. We love the product, but the upgrade has been a bit of a struggle.



        З найкращими побажаннями,
        Jamie

        Comment

        • yuri
          EspoCRM product developer
          • Mar 2014
          • 9225

          #5
          Hi Jamie,

          We have never shipped builds with the composer.json. The upgrade is supposed be run smoothly just by running the upgrade command. We host many instances, we constantly upgrade them just by running the upgrade command and have never had any problems.

          Problems usually arise when there are some manual customizations that are incompatible with the new version. 8 => 9 is the major release jump. There were some incompatibility breaks (available in GitHub release notes).

          What errors do you get when you run bin/command upgrade ?
          If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

          Comment

          • jamie
            Junior Member
            • Aug 2025
            • 4

            #6
            Hi Yuri,

            I do wonder why you don't ship with composer.json and the tests folder? as some one that wants to customize your lovely product they would be most useful

            i've got to copy over from our production site to the dev server and that will take a few hours so i don't be able to give accurate errors right now but the first one was with symfony/mailer and then a later one couldn't find Espo\Binding then i broke it badly trying to fix that and had to reset all the files after i dif the above method suggested by ai

            tomorrow morning everything should be copied over for me to try again and i shall share some accurate errors with you then

            thanks so much for your time have a great night

            Comment

            • yuri
              EspoCRM product developer
              • Mar 2014
              • 9225

              #7
              The product first caters for non-developers. It's even possible to upgrade via the UI. It's supposed to be built from the repository. Other software that is compiled is also shipped without dependency definitions and it's ok.
              If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

              Comment

              • yuri
                EspoCRM product developer
                • Mar 2014
                • 9225

                #8
                For customization, we recommend to use the extension approach.

                You can also use the repository directly and customize upon it. But in this case, the data and customization migration work lies on the user (developer).

                With the official approach, all the migration work is performed with upgrade script and we try to do our best to make such migrations smooth for users. Those who don't manually customize their instance much, or customize but wisely, usually don't have issues with upgrades. There are some other similar software where every upgrade is a huge endevour.
                If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

                Comment

                Working...