Imported the wrong file, mapped a column to the wrong field, or accidentally overwrote good data with an "Add and Update" import? This article covers how to prevent that situation, how to assess the damage, and your options for recovery.
The short version: TrackVia does not have a one-click "undo import" button. Your best protection is a backup taken before you import. If you're reading this after a bad import and don't have a backup, skip to "Recovering without a backup" and contact TrackVia Support — do not run additional imports in the meantime.
Prevent it: three habits before every significant import
Back up your account first. An account backup taken immediately before an import is the only guaranteed way to return to your pre-import state. See How to Backup and Restore Your Account. For large or high-stakes imports, treat this as mandatory.
Test in a sandbox. If you have a sandbox available, run the import there first and inspect the results before touching production. See How to Create a Sandbox.
Start with a small sample. Import the first 5–10 rows of your file as a trial. Check that dates, drop-downs, and relationship links landed correctly, then delete the sample records (or update them in the full run) and import the full file.
Assess: figure out exactly what the import did
Start with the import results email from TrackVia (no-reply@trackvia.com) and the Results tab of the import wizard. Both tell you how many records were added, how many were updated, and how many errored, and let you download the detailed error report.
To see the affected records, create a temporary view on the table filtered by the record creation or last-updated timestamp [VERIFY: exact system field names available for filtering] covering the time of the import. This shows you precisely which records the import touched. See How to Create Views.
Recover
Option 1 — Restore from your pre-import backup. This returns the account to its state at the time of the backup. Important: a restore affects your whole account, not just one table, so any changes made anywhere in the account after the backup will be lost. See How to Backup and Restore Your Account.
Option 2 — Bulk-delete records that were added. If the bad import only added records (Add Only), filter a view to the imported records as described above, then delete them. Consider exporting the view first as a safety copy.
Option 3 — Re-import corrected values over the bad ones. If the import updated existing records with wrong values and you have a file containing the correct values (for example, an export taken before the import), you can repair the damage by running an Update Only import with the corrected file. The file must contain the table's Record ID components so rows match. See How to Import to an Existing Table.
Option 4 — Contact TrackVia Support. If none of the above fits your situation — or an import is still running and you need it stopped — contact TrackVia Support. Note that stopping an in-progress import always requires Support's assistance.
Recovering without a backup
If you have no backup and Option 2 or 3 doesn't apply, gather the following before contacting Support, since it will speed up the investigation: the import results email, the error report download, the file you imported, the approximate time of the import, and which import type you selected (Add Only, Add and Update, or Update Only).
Comments
0 comments
Please sign in to leave a comment.