This article provides guidance for customers who intend to make a change within their infrastructure that requires mapping data from their existing system database to a new system database.
If you are considering any of the following scenarios, review the information in this article and be prepared to work with Higher Logic to ensure the smoothest possible migration.
- We plan to migrate from our current AMS/CRM database to a different AMS/CRM database and we want the least disruption within our integration with Higher Logic.
- We are planning a migration project from one Higher Logic community configuration (Standalone, Integrated, Upload) to a different Higher Logic community configuration.
- We are changing our unique identifier / primary key to be a different set up.
Changing a Unique Identifier or AMS/CRM: Risks & Recommendations
If you plan to change your AMS/CRM database or unique identifier (UID), review the information in this section.
Risks
- Loss of Access: The SSO login depends on endpoints and unique identifiers for authentication. If any of these change without notice, the ability to log in to your community will not be available.
- Broken Links: Other systems may lose the ability to connect data properly.
- Duplicate Records: New UIDs might create new records instead of updating existing ones.
- Lost History: Reports and tracking may lose historical data tied to the old UID.
- Integration Failures: APIs and syncs might break if they expect the old UID format.
What Higher Logic will work on with you
- Map All Dependencies: Find everywhere the UID is used and how it's shared across systems.
- Plan a Safe Transition: Use a mapping between old and new UIDs or temporarily support both.
- Test First: Try the change in a sandbox to avoid surprises.
- Notify Stakeholders: Notify teams and partners; update relevant documentation.
- Monitor After Changes: Watch for sync errors, duplicates, and data gaps.
AMS/CRM database migration caution
It's important to understand that migrating from one AMS/CRM database to a different one will compromise the "integration" between your AMS/CRM environment and your Higher Logic account if the necessary preparation has not been done.
Therefore, it is imperative that you notify Higher Logic of your migration plans at least 10 weeks in advance, so that we can assign resources and be prepared to assist you with the transition. This will ensure the least disruption to your integration and your SSO functionality.
Help us to help you
In order for us to do our best to assist you with your migration, create a case with Higher Logic Support and provide the following preliminary information regarding your migration project.
- Which AMS/CRM solution are you migrating to (include the version)?
- What is your current targeted "go live" date for the new AMS/CRM solution?
IMPORTANT: Higher Logic requests that you alert us at least 10 weeks in advance of your planned "go-live" date in order to ensure that our AMS Migrations team can schedule your migration.
- What is the cutoff date for your current AMS/CRM solution?
What's next?
When Higher Logic Support receives your request, they will escalate it to our AMS Migrations team and they will be in touch with you to discuss:
- next steps,
- anticipated costs, and
- timelines.
NOTE: Your prompt response ensures that we get your project scheduled and coordinated more quickly and decreases the likelihood of delays.