OroCRM Forums

Covering OroCRM topics, including community updates and company announcements.

Forums Forums OroCRM OroCRM – Installation/Technical Issues or Problems OROCRM migration to another server

This topic contains 2 replies, has 2 voices, and was last updated by  Matej 1 year, 11 months ago.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

  • Creator
  • #37514



    We will move the OroCRM 2.5. installation to another server. I have some concers about proper working of OROCRM app on new machine.

    Let’s purpose that the server “environment” will be the same.

    What else should I be aware of?

    Now we have enabled a:
    – Magento integration (one way – remote wins).
    – Mailchimp integration
    – We have cca. 15 users and lot of emails (all set up via IMAP).

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
  • #37515
    Yevhen Shyshkin
    Yevhen Shyshkin

    Hello, Matej.

    In general it’s enough to migrate file system and database. Here are several advices that might be useful during the migration to another server.

    1) Make sure you’re using the same secret key from app/config/parameters.tml
    2) Make sure you’ve copied all attachments from app/attachment directory
    3) If you’re changing domain name you have to change it at the DB as well – see table oro_config_value
    4) Turn on maintenance mode at the old server before the upgrade, so users will not have an access to it during the upgrade
    4) After you’ve copied all required files and rolled back DB dump it recommended to follow standard upgrade procedure to warm up all required caches and generate required files – https://oroinc.com/orocrm/doc/2.6/dev-guide/cookbook/how-to-upgrade-to-new-version
    5) If you’re using Elasticsearch and you’re going to use new instance you have to reindex all the data using oro:search:reindex command
    6) If you’re using RabbimMQ and you’re going to use new instance please wait for all messages to be processed and only then enable maintenance mode – so message queue should remain empty during the upgrade process
    7) It’s recommended to keep old server at maintenance mode after the upgade, so users will not work with the old instance
    8) Make sure that cron, consumers and web socket server set up and work properly at the new instance
    9) Check all types of logs (application, consumer, cron, DB, search engine, message queue) during the first several hours/days after the upgrade

    As fot the integrations – they should work fine as configuration and data are stored at the DB. Just make sure that new server has access to the required resources and 3rd party servers allow access from your new host/IP-address.

    Please, let me know if you still have some question.



    Thank you for detailed check list.

    Best regards.

Viewing 2 replies - 1 through 2 (of 2 total)

The forum ‘OroCRM – Installation/Technical Issues or Problems’ is closed to new topics and replies.

You will be redirected to [title]. Would you like to continue?

Yes No