{"id":89582,"date":"2025-10-22T09:10:22","date_gmt":"2025-10-22T08:10:22","guid":{"rendered":"https:\/\/churchtools.academy\/help\/non-knowledgebase\/uncategorized\/troubleshooting-after-migrating-to-dgm-2-0\/"},"modified":"2026-08-12T13:24:25","modified_gmt":"2026-08-12T12:24:25","password":"","slug":"troubleshooting-after-migrating-to-dgm-2-0","status":"publish","type":"docs","link":"https:\/\/churchtools.academy\/en\/help\/framework-agreement-partner\/evangelical-regional-church-in-wuerttemberg\/troubleshooting-after-migrating-to-dgm-2-0\/","title":{"rendered":"Troubleshooting after migrating to DGM 2.0"},"content":{"rendered":"\n

The new DGM 2.0 is here and is gradually being rolled out to all congregations. The DGM, DataGroup, and ChurchTools are working closely together on this. However, minor migration issues cannot be avoided. On this page, we describe potential issues that may arise in ChurchTools after migrating to DGM 2.0 and explain how you can resolve them. <\/p>\n\n\n\n

Problem: Features are unavailable or data is not visible<\/h2>\n\n\n\n

Your portal profile will be migrated to the new DGM 2.0. In most cases, you won\u2019t even notice that a migration has taken place, except that you\u2019ll now log in to the portal through Microsoft.
Once you\u2019ve successfully logged in to ChurchTools via the new portal, your existing ChurchTools profile will be linked to or updated with your new portal profile. <\/p>\n\n\n\n

If, after Login, some features are unavailable or data is no longer visible, you may be missing permissions in ChurchTools. This can happen if your existing ChurchTools profile has not been linked to your new portal profile. As a result, ChurchTools was unable to find a matching user and created a new user with limited permissions. <\/p>\n\n\n\n

Why does this happen?<\/strong> <\/p>\n\n\n\n

In most of the cases we’ve observed, the problem was caused by umlauts in the name. For example, if the last name is M\u00fcller, it\u2019s possible that the last name is stored in the portal as \u201cMueller.\u201d As a result, the two last names are no longer identical, and ChurchTools interprets this as a new person and creates a new person record for it. <\/p>\n\n\n\n

In other cases, the ELWK e-mail address stored in ChurchTools is not the same as the one in the portal. Since ChurchTools compares records based on first name, last name, and e-mail address, this can result in a new person record being created. <\/p>\n\n\n\n

How can this problem be solved?<\/strong> <\/p>\n\n\n\n

Currently, only ChurchTools Support can resolve this issue. Please use the contact form<\/a>, let us know the name of the person affected, and which system is involved (ChurchTools URL: this starts with elkw<\/code> followed by 4 numbers). <\/p>\n\n\n\n

Problem: Unable to perform login<\/h2>\n\n\n\n

If you are unable to log in to ChurchTools after the DGM 2.0 migration, it may be because duplicate entries have been created in ChurchTools, preventing the automatic assignment of profiles.<\/p>\n\n\n\n

How can this problem be solved?<\/strong><\/p>\n\n\n\n

The local ChurchTools administrator will be notified of this issue via e-mail. Duplicates should be avoided in ChurchTools as much as possible. The administrator can resolve this issue themselves in the Persons module using the ” Check duplicates<\/em> ” (1) feature. Therefore, please contact your local administrator first.<\/strong> <\/p>\n\n\n\n

\"Screenshot<\/a><\/figure>\n\n\n\n

“Person status: Unknown<\/em> ” as the new standard<\/h2>\n\n\n\n

The new DGM 2.0 simplifies the process of gaining access to a ChurchTools system, allowing individuals to assign themselves to a church on their own. This enables staff members to gain access to their system more quickly. <\/p>\n\n\n\n

To prevent unauthorized individuals from accessing personal data from other systems, the default person status<\/em> has been changed. This means that new users who log in to ChurchTools will be assigned the “Unknown<\/em>” person status going forward. <\/p>\n\n\n\n