When you archive a record, delete a profile, or remove a piece of information (like an email or phone number) from a constituent in Almabase, a natural question is: "What happens on the Raiser's Edge side?"

The answer depends on whether you're acting on the record itself (archiving or deleting the whole profile) or on a piece of information within the record (removing an email, phone number, or address). These two scenarios are handled very differently.

For record-level actions, Almabase takes a conservative approach — it never pushes record deletions or status changes to RE.

For information-level removals, your sync rules control what happens. Understanding the distinction helps you manage your data confidently across both systems.

Almabase gives admins two ways to remove a constituent from the active directory:

When you remove a specific piece of information from a constituent's Almabase profile — say you delete an outdated phone number or an old email address — the behavior depends on your Delete sync rule for that entity in the Almabase → RE direction.

You can find these settings at Settings → Database → Sync Rules. For each entity (emails, phones, addresses, etc.), there's a Delete rule with three options:

Maria Gonzalez's work email (maria@oldcompany.com) starts bouncing. You remove it from her Almabase profile. Here's what happens next:

Note: Inactive records or fields are not pulled from RE to Almabase during a data pull. However, if a record was already pulled into Almabase and is later marked inactive in RE, that status change has no effect on the Almabase profile — it remains active until you manually archive it.

Because removed data is difficult to recover — especially in Raiser's Edge, where restoring a deleted email or address requires manual re-entry — we recommend setting the Delete sync rule to "Review before deleting" for most entities in the Almabase → RE direction.

This gives you a safety net. If someone accidentally removes a phone number or email from an Almabase profile, you catch it in the Data Inbox before it propagates to your database of record.

No. Almabase never deletes constituent records in RE, regardless of what happens on the Almabase side — whether you archive or delete the profile. This is a permanent safety protection.

Archiving marks the profile as inactive — the record still exists in Almabase, can be reactivated, and its history is preserved. Deleting permanently removes the profile from Almabase and cannot be undone. In both cases, the RE record is not affected, and any pending sync changes for that profile are cleared.

The re-pulled profile will have whatever data exists in RE at the time of the pull. Any Almabase-only data (like event registrations or email engagement that was never synced to RE) from the old profile is not carried over — it was removed when the profile was deleted.

If the removal has already synced to RE (because your Delete rule was set to "Delete Automatically"), you'll need to manually re-add the email address in Raiser's Edge. This is why we recommend the "Review before deleting" sync rule — it gives you a chance to catch mistakes before they reach RE.

Remove the System Record ID from their Almabase profile. This severs the link between the Almabase and RE records, so no changes flow in either direction. The profile remains active in both systems but is no longer connected.

No. The Delete sync rule only governs information-level removals — deleting an email, phone number, address, or other entity from a profile. Archiving or deleting the record itself is not controlled by sync rules.