How to get the SugarCRM downloaded in local machine ? Store site is redirceting me to user page.

Hi there,

I have got free trail link. I'm unable to download the SugarCRM from the store site which is mentioned in the documentation. It navigates me to user link instead. Can you please throw us some light on how to download it and run on a local machine ?

Appreciate the assistance in advance. Thanks.

Parents
  • Hi Manimaran,

    Free trials do not provide access to the download the software. They are only available through Sugar's hosted service. You need to speak to Sugar sales if you wish to evaluate the software for on-site use.

  • Thank Chris Raffle for taking your time to reply, Appreciate it. We did evaluate the free trail. We already have an application up and running in Community edition. Is there a way to upgrade from community edition to the SugarCRM standard edition withour interrupting any existing fields and database structure ? We would love to hear back from you on this and appreciate all your inputs in advance. Thanks.

  • Hi Manimaran,

    I already replied above. Please review and let me know if you have any questions. Thanks!

  • Thanks for the reply Chris Raffle , my bad not sure how it ended up in two comments. We will take a look at the link you have provided. Also, do we have any procedures to migrate the CE MySQL data to the latest version? We would love to hear back from you on this and appreciate all your inputs in advance. Thanks.

  • Hi Manimaran,

    Assuming you opt to move forward with upgrading the CE system to a commercial edition and then to the latest release, then I suggest mapping out the platform upgrades through the appropriate path you need to take. The Unsupported Versions documentation contains an archive of the supported platforms for each older version. 

    I recommend that you perform any necessary platform upgrades before upgrading Sugar. For instance, let's say you are currently running Sugar 6.5.20 CE with MySQL 5.5, PHP 5.2, and elasticsearch 0.90.10. Your upgrade process would begin like this:

    1. Upgrade Sugar from 6.5.20 CE to 6.5.26 CE (No platform changes required since you remain on the same base version of Sugar)
    2. Convert Sugar from 6.5.26 CE to 6.5.26 Pro or Ent (No platform changes required since you remain on the same base version of Sugar)
    3. Upgrade PHP from 5.2 to 5.3 since Sugar 7.7 does not support PHP 5.2
    4. Upgrade elasticsearch from 0.90.10 to 1.4.4
    5. Upgrade Sugar from 6.5.26 to 7.7.2.2 (No MySQL upgrade required since Sugar 7.7 supports MySQL 5.5)
    6. Upgrade Sugar from 7.7.2.2 to 7.7.2.3 (No platform changes required since you remain on the same base version of Sugar)
    7. Upgrade PHP from 5.3 to 5.6 since Sugar 7.8 does not support PHP 5.3
    8. Upgrade MySQL from 5.5 to 5.6 since Sugar 7.8 does not support MySQL 5.5
    9. Upgrade Sugar from 7.7.2.3 to 7.8.2.2 (No elasticsearch upgrade required since Sugar 7.8 supports elasticsearch 1.4.4)
    10. etc...
    11. etc...
    12. Upgrade to Sugar 9.0.2

    Note: When upgrading to Sugar 8.0, there is a major upgrade of elasticsearch that cannot be performed in the above method. Please refer to the 8.0 installation and upgrade guide when you reach that stage to properly handle the elasticsearch upgrade.

    If you instead opt to install a new instance of Sugar Pro/Ent on the latest release, then I strongly recommend using the in-app export and import utilities where possible since you can use the UI to map the data to the appropriate fields. There are a lot of schema changes between 6.5 and 9.0 so trying to migrate all data via SQL would be problematic. The drawback from using the in-app import utility is that you would still need to migrate some specific elements from Sugar via database queries (e.g. many-to-many relationships).

Reply
  • Hi Manimaran,

    Assuming you opt to move forward with upgrading the CE system to a commercial edition and then to the latest release, then I suggest mapping out the platform upgrades through the appropriate path you need to take. The Unsupported Versions documentation contains an archive of the supported platforms for each older version. 

    I recommend that you perform any necessary platform upgrades before upgrading Sugar. For instance, let's say you are currently running Sugar 6.5.20 CE with MySQL 5.5, PHP 5.2, and elasticsearch 0.90.10. Your upgrade process would begin like this:

    1. Upgrade Sugar from 6.5.20 CE to 6.5.26 CE (No platform changes required since you remain on the same base version of Sugar)
    2. Convert Sugar from 6.5.26 CE to 6.5.26 Pro or Ent (No platform changes required since you remain on the same base version of Sugar)
    3. Upgrade PHP from 5.2 to 5.3 since Sugar 7.7 does not support PHP 5.2
    4. Upgrade elasticsearch from 0.90.10 to 1.4.4
    5. Upgrade Sugar from 6.5.26 to 7.7.2.2 (No MySQL upgrade required since Sugar 7.7 supports MySQL 5.5)
    6. Upgrade Sugar from 7.7.2.2 to 7.7.2.3 (No platform changes required since you remain on the same base version of Sugar)
    7. Upgrade PHP from 5.3 to 5.6 since Sugar 7.8 does not support PHP 5.3
    8. Upgrade MySQL from 5.5 to 5.6 since Sugar 7.8 does not support MySQL 5.5
    9. Upgrade Sugar from 7.7.2.3 to 7.8.2.2 (No elasticsearch upgrade required since Sugar 7.8 supports elasticsearch 1.4.4)
    10. etc...
    11. etc...
    12. Upgrade to Sugar 9.0.2

    Note: When upgrading to Sugar 8.0, there is a major upgrade of elasticsearch that cannot be performed in the above method. Please refer to the 8.0 installation and upgrade guide when you reach that stage to properly handle the elasticsearch upgrade.

    If you instead opt to install a new instance of Sugar Pro/Ent on the latest release, then I strongly recommend using the in-app export and import utilities where possible since you can use the UI to map the data to the appropriate fields. There are a lot of schema changes between 6.5 and 9.0 so trying to migrate all data via SQL would be problematic. The drawback from using the in-app import utility is that you would still need to migrate some specific elements from Sugar via database queries (e.g. many-to-many relationships).

Children
No Data