When you pull constituent data from Raiser's Edge NXT into Almabase, most records come through cleanly — but some may hit errors along the way. This is normal, especially with large pulls.

Errors don't stop the pull. Almabase processes each record independently, flags the ones that failed, and moves on. When the pull finishes, you can review the errors, fix the underlying issues, and retry just the failed records without re-pulling everything.

After a pull completes, go to Settings → Database → Sync Data. The pull history shows every pull you've run, with the date, the list or query used, and the counts: total records, successful, and errors. Click into a pull session to see the errors.

Errors are split into two categories:

Errors affecting multiple constituents — These are errors where a single issue caused failures across multiple records. For example, an unsupported dropdown value in RE that doesn't have a matching option in Almabase — every record with that value fails for the same reason. Fixing the one underlying issue resolves all the affected records at once.

Errors affecting individual constituents — These are one-off errors specific to a single record. For example, a rate limit from RE's API, or a data formatting issue on one particular constituent. These need to be reviewed and resolved per constituent.

Each record in a pull is processed independently — constituent by constituent. Within each constituent, the system pulls data entity by entity: basic information first, then emails, phone numbers, addresses, education records, and so on. If one entity fails (say, an education record has an unrecognized degree value), the rest of that constituent's data can still come through successfully.

This means a single constituent can be partially pulled: their profile and email might be created in Almabase, but their education record might show up as an error. These are called partial errors — the constituent exists in Almabase, but some of their data didn't make it.

Here are the errors you're most likely to see after a pull, and what each one means:

Unsupported values (dropdown mismatch) — This is the most common error. It happens when a field value in RE doesn't have a matching option in Almabase. For example, if RE has a degree value of "BS in Engineering" but Almabase doesn't have that option in its degree dropdown — the system can't map it, and the record fails. The error message tells you which field and which value caused the problem.

How to fix it: Click Fix Errors on the error — Almabase shows you the missing values and lets you add them right there. Then click Add values and re-pull constituents to add the values and retry in one step. If a matching value already exists in Almabase and the error still shows, reach out to our Support team — they'll get it sorted.

Rate limit exceeded after multiple retries — Almabase tried to fetch data from RE's API but was rate-limited, and the retries didn't succeed. This is usually a temporary issue — RE's API was under heavy load at the time of the pull.

How to fix it: Click Fix errors on the affected constituent, then click Resync record to retry. If the error persists, wait a few minutes and try again, or reach out to our Support team.

Error fetching records from external database — Almabase couldn't retrieve the data from RE's API. This is similar to rate limiting — RE's API may have been slow or returned an error for that specific record.

How to fix it: Wait a few minutes and retry the failed records. If the error persists, check that your RE NXT connection is still active at Settings → Database, or reach out to our Support team.

Ignoring errors: If an error isn't relevant — for example, a field value you don't need in Almabase — you can click Ignore to dismiss it. The constituent's profile stays in Almabase with whatever data did come through successfully; only the ignored entity is skipped.

Tip: For errors affecting multiple constituents, fix those first. A single dropdown fix can resolve dozens of errors at once.

The pull still succeeded for the records that didn't have errors. Almabase processes each constituent independently — if 950 out of 1,000 records succeeded and 50 had errors, those 950 records are in Almabase and fully usable. Only the 50 with errors need attention.

Yes. This is called a partial error. The constituent's basic information (name, ID) and other entities like emails may have come through fine, but one specific entity — like education — hit an issue. The profile exists in Almabase; it's just missing that one piece of data. Fix the underlying issue and retry to fill in the gap.

Yes — errors affecting multiple constituents are grouped by error type, so you can fix one group at a time. For example, if you have an unsupported dropdown value that affected 30 records, clicking Fix Errors on that group lets you add the missing value and re-pull just those 30 records without touching errors from other groups.

Reach out to our Support team — they'll help you figure out what's going on and get it resolved.

Ignoring an error dismisses it from the error list. The constituent's profile and any data that pulled successfully stays in Almabase — you're only skipping the specific entity that failed (like one education record or one phone number). Use Ignore when the errored data isn't needed in Almabase.

You can retry immediately after making the fix in Almabase (like updating a field mapping or adding a dropdown value). If the issue was on the RE side and you've updated the record there, wait a few minutes for the change to be available through RE's API, then retry.

No. Pull errors are specific to the pull process — they don't block or interfere with the regular ongoing sync. Once a constituent is successfully pulled into Almabase (even with partial errors), changes to their existing data in RE will flow to Almabase based on your sync rules as usual.