Migrating to iGrafx Cloud
Migrating to iGrafx Process360 LiveProcess360 Live iGrafx's cloud platform for end-to-end process management — combining process design, mining, simulation, and automation in a single environment. Cloud moves your on-premises repository into an instance that iGrafx hosts and maintains. iGrafx restores a backup of your repository database in the Cloud and registers it. Your repository content arrives unchanged. iGrafx migrates the repository database only: you configure platform administration (users, sign-in, security roles, licenses, and platform settings) again in your Cloud instance, which is ready for you before the repository arrives.
Overview
iGrafx Support plans these steps and their timing with you.
- Plan. You open a migration ticket with iGrafx Support, agree on the migration window, and say whether you want a test migration before the final one. In the ticket, iGrafx Support gives you the link to a secure upload location for your backup.
- Configure your Cloud instance. iGrafx has already provisioned it. You configure sign-in, provision users and groups, and copy your security roles, license assignments, and customizations from your on-premises platform. None of this needs the migrated data, so start as soon as you have access. To keep your item permissions and resource links, do this before iGrafx registers the repository: registration matches users, groups, and item roles by name, and removes whatever doesn't match.
- Prepare. You change on-premises usernames to the email addresses the accounts use in the Cloud.
- Test migration (optional). If you agreed on one, you export the repository database as a bacpac file and upload it through the upload link from your ticket, and iGrafx restores it into your Cloud instance so you can validate the result. Your on-premises platform stays in use meanwhile, so switch off email notifications in the Cloud instance for the test duration, or your users receive notifications from both.
- Final migration. You export and upload a final backup the same way. Anything changed on-premises after that backup isn't in the Cloud, so limit the on-premises platform to viewing from that moment on. iGrafx restores and registers the backup, you verify the result, and you confirm in the ticket. iGrafx then closes the migration, and you update links in your content that contain the on-premises hostname.
Keep your on-premises platform running until you've confirmed the final migration; it's your fallback. See the rollback procedure.
What migrates and what you recreate
The repository database holds your content; the administration database holds the platform setup. Only the repository database migrates.
| Migrates unchanged | You recreate in the Cloud |
|---|---|
| Folder hierarchy | Users and groups, directories |
| Diagrams and documents, including approved and historical versions | License assignments |
| Objects, their properties, and their relationships | Server and repository roles, and their assignments |
| Resources, organizations, and RACI assignments | Server settings |
| Custom properties | Email settings and templates |
| Governance cycles, cycle groups, and their history | Customizations: theme and narrative export theme, dynamic links, localized property names, and the User Display Names format |
| Landing pages | API keys |
| Repository settings, including the repository theme and default narratives | User preferences |
| Item permissions, if mapped | Item roles with their on-premises names |
User audit data stays in your on-premises platform; it isn't migrated.
The repository refers to users by username, and to groups and item roles by name. When iGrafx registers the repository, it matches each of them against what exists in the Cloud:
- A user account matches when a Cloud username equals the on-premises username, ignoring case. A matched account keeps its item permissions, checkouts, governance roles, to-dos, and notifications.
- A group or item role matches by name. Item permissions, cycle-group memberships, and notifications that refer to an unmatched group or item role are removed.
- A user's link to a resource is kept only if the Cloud username matches exactly, including case. See Map users to resources.
What changes for your users
- The URL. Your instance gets a new hostname. Repository links keep working, but any link that contains the old hostname points at the old platform: browser bookmarks, links in intranet pages, links embedded in documents, REST API endpoints, and the links in every notification email received before the migration. iGrafx doesn't redirect the old hostname. Ask your IT team whether a redirect is an option for you; it helps with bookmarks and emailed links but doesn't fix links embedded in documents or API endpoints. What effect does changing the site URL have on my content lists what is affected.
- First sign-in. Every user accepts the iGrafx Subscription Services Agreement the first time they sign in.
- Desktop clients. Installed desktop clients connect to the Cloud URL in the same way they connected on-premises. Ask desktop client users to check in before the final backup, so their changes are in it.
Who does what
From the migration ticket until you confirm the final migration, the work splits as follows.
You:
- back up and upload the repository database, for a test migration and for the final migration
- configure sign-in, users, groups, security roles, licenses, and platform settings
- validate each restored repository, and confirm the final migration
- reconnect your integrations with new API keys and the Cloud hostname after the final migration
- tell your users about the new URL
- keep the on-premises platform running as your fallback until you've confirmed the final migration
iGrafx:
- provides the secure upload location and agrees on the migration window with you
- restores each backup and registers the repository in your Cloud instance
- configures iGrafx IdentityiGrafx Identity The iGrafx identity and access management service that brokers authentication between customer identity providers and Process360 Live components. for your single sign-on, if you use it
Related tasks & references
- Migrate your repository to iGrafx Cloud: the phased procedure with its verification checklist.
- Setting up Single Sign-On
- Synchronizing your user base: automatic user provisioning with SCIM.
- Platform Administration: everything you set up again in the Cloud.
- Upgrading the iGrafx platform: bring a platform older than version 19 up to date before migrating.