New

See what a re-import kept your version of

When an import finds a field you edited that also changed at the source, it keeps your version — and now says so on the Integrations screen, with the option to take the source value instead.

A re-import already protects your edits. If you renamed a client here and the name also changed in Harvest, the import keeps your name rather than overwriting it.

What it did not do was tell you. The detail went into a server log and you got a number, so "did the import overwrite my change" had no answer you could see.

Integrations → Kept your version now lists them: which client, project or task, which field, your value and the source's, and when it was noticed.

Nothing here needs doing

Every row is a decision already taken, and taken the right way round. The list exists so you can disagree, not because something is waiting on you.

  • Keep mine records that you looked and agreed.
  • Use the source value writes the source's value over yours and stops that field conflicting in future — it starts tracking the source again.

Re-importing weekly does not pile up copies: a field that keeps disagreeing stays one entry, with the date it was last seen. A fresh disagreement after you have settled one is a new entry, because it is a new event.

Why it is worth glancing at

One row is somebody's edit being protected. The same row appearing every week means an import is quietly declining the same change indefinitely, which usually means the two systems disagree about something that should be settled in one of them.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free