Upgrade to the Enterprise plan

with the enterprise plan, you get access to the most advanced {{product name}} features, wider limits, priority support, and a separate celonis amazon web service environment after signing up for enterprise, you will need to migrate your data to our dedicated server in your region this will give you access to a more stable and reliable infrastructure {{product name}} provides an effective tool to let you migrate your data fast and easily in this article, you will learn how to use the {{product name}} migration tool to move your data and start enjoying the enterprise plan migration scope overview the migration tool has two modes fast mode enables automatic migration of selected {{scenario plural lowercase}} and their associated data in some cases, the system may require you to take manual steps manual mode allows you to choose which data to migrate and how to handle it in your enterprise instance which data can you migrate? the migration tool migrates the following items {{scenario plural}} and {{scenario singular lowercase}} folders connections (except those that are associated with on premise agent docid 2d2 hut5eujnkigszp0vm webhooks and mailhooks keys data stores data structures custom apps if the following items exist in your source instance, but no {{scenario plural lowercase}} use them, the migration tool doesn't move them to the target instance connections webhooks and mailhooks keys data stores data structures which data can't you migrate? user accounts organizations {{scenario singular}} executions history and logs incomplete executions upgrade to the enterprise plan docid\ afqxzv wywkylberqkwbv webhook and mailhook queues and logs upgrade to the enterprise plan docid\ afqxzv wywkylberqkwbv upgrade to the enterprise plan docid\ afqxzv wywkylberqkwbv prepare your data the migration tool has some peculiarities that you need to keep in mind when migrating your data either in fast or manual mode to arrange your target instance better, consider taking some measures that allow you to overcome limits of the migration tool teams keep in mind that migration involves transferring data from one team in the source instance to another team in the target instance to have your data in different teams in the target instance in the target instance, create as many teams as needed in the migration tool, select the team you want to migrate scenarios to, and then select the specific {{scenario plural lowercase}} to be moved to the selected team you can't move {{scenario plural lowercase}} from one team to another after finishing migration when migration is complete, you can clone {{scenario plural lowercase}} and select the desired team for them to avoid data inconsistency, we recommend not migrating data from the same team more than once time zones keep in mind that the migration tool doesn't migrate the time zone settings you need to set up time zones in the target instance if you aim to run {{scenario plural lowercase}} in the target instance according to the time zone that you have in the source instance, manually set up a time zone in the target instance learn more about manage time zones docid\ bn3s0 8azjdynxbnznp a scenarios keep in mind that if your {{scenario plural lowercase}} contain apps that require you to whitelist ip addresses for access, you need them to have relevant ips associated with the target instance before migrating such scenarios, allow connections to and from make ip addresses docid\ d0fwd60kzrvcj9b0ozriy depending on your zone eu1 make celonis com or us1 make celonis com you may delete those ips from apps in the source instance after the migration is done keep in mind that the migration tool doesn't migrate a webhook or mailhook queue it can cause problems if you use webhooks docid 1yhunj8jvzyxip9cf3ps1 because {{scenario singular lowercase}} data may arrive to the target instance before the queue is processed in the source instance to ensure sequential processing, do one of the options option 1 process the entire queue in the source instance before migrating option 2 migrate {{scenario plural lowercase}} in the manual mode disable {{scenario plural lowercase}} in the target instance and enable {{scenario plural lowercase}} in the source instance process the webhook queue once all the data is processed, enable {{scenario plural lowercase}} in the target instance data received after migration goes to the new webhook url and will be processed once you enable {{scenario plural lowercase}} in the target instance connections keep in mind that the migration tool doesn't replace one connection with another if they have different scopes and permissions ensure that scopes and permissions of connections in the target instance match scopes and permissions of connections that you want to replace data stores keep in mind that data may be inconsistent between the source and target instances if the migration tool moves {{scenario plural lowercase}} that update data stores more frequently than every five minutes to avoid inconsistency stop all {{scenario plural lowercase}} in the source instance before starting migration you only have to stop {{scenario plural lowercase}} that contain the add/replace a record , delete all records , delete a record , and update a record modules migrate the {{scenario plural lowercase}} run the {{scenario plural lowercase}} in the target instance custom apps keep in mind that you cannot migrate {{scenario plural lowercase}} with published custom apps if you didn't install those apps into the target instance beforehand to have {{scenario plural lowercase}} with custom apps in the target instance if the custom app has the private status, publish it refer to the app builder documentation to learn more it is not possible to migrate apps that have the private status publish the app after making all the necessary changes when the custom app has the published status, you cannot make the custom app private again delete the custom app delete a module from the custom app install the published custom app in the target instance delete a module from the custom app migrate your data you can migrate as many {{scenario plural lowercase}} as you want at once if you don't migrate all {{scenario plural lowercase}} at once, you can continue later follow the next steps to start migration go to the migration tool read all the information and click let's start in the source and target sections, select {{product name}} in both sections, click sign in to source and sign in to target respectively, and log in to both {{product name}} instances then click continue in both organization dropdown lists, select the source organization to migrate data from, and the target organization to migrate the data into in both team dropdown lists, select the source team to migrate data from, and the target team to migrate data into then click continue you see the list of all {{scenario plural lowercase}} that your source instance has you can select the migration mode fast or manual you see the list of all {{scenario plural lowercase}} that your source instance has you can select the migration mode fast or manual the migration tool doesn't migrate s {{scenario plural lowercase}} that have errors you can find them in the non migratable {{scenario plural lowercase}} tab if you want to move those {{scenario plural lowercase}} to the target instance, you must first resolve the errors manage your data and finish the migration depending on the migration mode you chose, you need to decide how to handle your data from the source instance some options are available only for the manual mode we highly recommend using the fast migration mode to ensure smooth and easy data transferring select custom apps to replace ones that migrated {{scenario plural lowercase}} use select the action for connections duplicate a connection in the target instance replace a connection with the one that exists in the target instance use a previously migrated connection the set of scopes or permissions of a particular connection might differ between the source and the target instance to see the scopes of a specific connection, go to the connection section and click the eye icon if you need to extend scopes log in to either a source or a target instance depending on where you need to extend scopes create a new {{scenario singular lowercase}} or open an existing one add a module that requires additional scopes create a new connection {{product name}} will ask you to provide additional permissions click continue on the app page where you're redirected to, confirm granting new scopes optional delete the module or the newly created {{scenario singular lowercase}} if you don't need it some apps allow adding scopes manually when creating a new connection if you created a custom application in a service itself, you may extend scopes in your service account select the action for webhooks and mailhooks duplicate a webhook or mailhook duplicate a webhook or mailhook and forward traffic we recommend always choosing the second option if you just duplicate a webhook or mailhook, traffic will still be sent on the webhook or mailhook that you have in the source instance, and no data will appear in the target instance a duplicated webhook will have a different url if you have linked devices in your source instance, create a mock device in the target instance you need to replace a mock device with a real device see more information in the upgrade to the enterprise plan docid\ afqxzv wywkylberqkwbv below select the action for data stores duplicate a data store and migrate its content duplicate a data store without its content replace a data store with the one that exists in the target instance the migration tool will replace data in the data store in the target instance with data from the source instance if you use auto generated keys, {{product name}} will store data under different keys in the target instance select the action for data structures duplicate a data structure replace a data structure with the one that exists in the target instance select the action for keys duplicate a key a duplicated key contains the relevant data, but the key id is different replace a key with the one that exists in the target instance select the action for folders duplicate a folder replace a folder with the one that exists in the target instance select what you want to do with the {{scenario plural lowercase}} both in the source and target instances if at least one {{scenario singular lowercase}} contains webhooks or mailhooks, {{product name}} automatically disables all migrated scenarios you may enable them manually after migration click start migration the migration tool shows the list of {{scenario plural lowercase}} and entities it migrated and confirms that the migration process was successful click show log to see the migration log if the migration fails, the migration tool rolls back all changes made both to the source and target instances check the migration log out to find out reasons for the failure post migration data setup using the migration tool to move your data to a different server environment ensures smooth and easy migration still, you must consider specific details and take certain actions after migration to fully benefit from the enterprise plan your data will remain in your source instance after migration subscriptions and coupons {{product name}} doesn't automatically cancel your source instance subscription after you fully set up your target instance, you need to manually cancel your subscription after that, your source instance moves to the free pricing plan https //www make com/en/pricing you can use all available features within this plan extra operations remain in the source instance contact our support to move extra operations to the target instance scenarios after migrating {{scenario plural lowercase}} scheduled as immediately , they execute once the {{scenario plural lowercase}} trigger receives new data some {{scenario plural lowercase}} require additional configuration after migration pay attention to {{scenario plural lowercase}} that contain custom apps they may require additional setup apps that require ip whitelisting make sure that the migrated scenarios have allow connections to and from make ip addresses docid\ d0fwd60kzrvcj9b0ozriy in their apps the {{product name}} app create a new connection and update all ids mapped in the app modules new ids should be associated with the data based on the target instance on prem connections the migration tool doesn't migrate connections associated with on premise agent docid 2d2 hut5eujnkigszp0vm you need to manually create connections in the target instance and then link them to connected systems webhooks and mailhooks if during migration you selected duplicating webhooks or mailhooks and forwarding traffic, the old url in the source instance still receives traffic, but redirects it to the new url in the target instance don't delete the old url in order not to lose traffic contact our support to receive a list of pairs of old and new urls devices the migration tool creates mock devices in the target instance to migrate {{scenario plural lowercase}} that use the ios or android app the mock device is called a deaf device in the target instance after migration, to use such {{scenario plural lowercase}} , you must create a new device manually in the target instance replace a mock device with the newly created in all relevant {{scenario plural lowercase}} delete all mock devices