Skip to main content
Data & integrations

Undoing an integration sync

Check whether a recent HR-system sync can be reversed, review the preview and resolve blocking conditions.

Written By Karl

Last updated 1 day ago

If a sync brought in data you didn't expect, for example after a mapping mistake, Undo Import may let you reverse its tracked changes. Not every sync can be undone; check the conditions and preview before proceeding.

Who can do this: Administrators.

Where: Settings → People & data → Integrations → your connection → Sync History

When you can undo

Look for Undo Import on the latest sync in Sync History. The sync must have completed or partly completed, must not be a Preview Run, and must not already have been undone.

The undo checks also require:

  • no later completed or partly completed, non-preview, unreverted sync for the same connection;

  • no pending or running sync for that connection;

  • recorded changes and the before-state information needed to restore updated records;

  • affected records that still exist and remain within the connection's permitted scope;

  • no detected conflicts, such as later modifications to affected records.

Evenpay plans the undo before applying it. A detected conflict or missing required information blocks the operation rather than automatically overwriting the conflict.

Before you start

Pause automatic syncing while you investigate and avoid editing affected records during the undo. See Managing a connection. Do not rely on undo as a substitute for checking changes made after the sync.

Steps

  1. Open the most recent sync in Sync History.

  2. Select Undo Import if available.

  3. Check the preview of records that will be removed because the sync created them, and records that will be restored because the sync updated them.

  4. If the preview reports a blocking reason, stop and investigate it. Contact support if the required action is unclear.

  5. When the preview allows the undo and the changes are appropriate, confirm Undo Import?.

Good to know

  • Undoing is recorded in each affected employee's history with the source Revert.

  • After the undo, check the affected records and fix the mapping or source-data issue before the next sync. Otherwise, the same unwanted data can return. Use Preview Run to check first.

  • If undo is blocked, do not assume that another import will safely reverse the earlier changes. Contact support with the connection, sync run and blocking reason.

Was this helpful?

Still need help? Share an idea