Recover imports and sync
Reconcile partial imports, fix source mapping and read saved sync outcomes before submitting work again.
Work out what arrived, what did not and whether another read or import is the right next action.
Find the original import#
Open Settings → Imports in the correct workspace. Find the import by its source, time and destination. Open its details before uploading anything again.
Keep the original file or authorised source available to you. Do not send a full contact list to an agent, public feedback or support simply to explain an error. Start with the import identifier, destination, status, counts, mapping and exact message.
If the import list or details cannot be read, retry the read. Keep the result unknown. Missing details are not proof that no rows were written or that it is safe to repeat the import.
The Imports list shows source records and incomplete outcomes before another submission.
Separate a saved source from its job#
An import is a job processing rows. A saved source retains the location, mapping, destination and schedule used for later checks. A source can be On while its latest import is waiting, running or stopped.
Choose Syncing to read the saved source. Check its Into destination, cadence, On or Off state, latest result and error. A recent source read does not establish a completed job or prove that every original row arrived.
The direct Google Sheet route is a one-way import into Kite. It does not establish two-way sync, a CRM write-back or deletion of contacts when a source row disappears. Use Read sources and sync status for the source controls.
The Syncing view shows source schedules, destinations and a refused latest read; no schedule or re-read control is pressed.
Read the actual outcome#
| Recorded state | What to do next |
|---|---|
| Queued or running | Inspect the existing job and wait for its recorded result before another request |
| Completed | Reconcile the written rows, skipped rows and reasons |
| Partial | Check what was already written and diagnose the remaining rows |
| Failed or stopped | Read the error and counts; do not assume the job made no changes |
| Missing or unreadable counts | Keep them unknown and reconcile current destination records before retrying |
A successful row can create a person or update an existing contact. A partial or stopped job may already have written usable rows. Repeating an import is not an undo, and it can update contacts again.
Keep the reported row categories distinct. File duplicates, invalid email, missing email and do-not-contact exclusions have different remedies. If a source total is missing, do not fill it in with zero or claim that the counts establish complete coverage.
The partial CSV record reports 388 written rows, 26 parser duplicates and 216 rows that did not arrive, with distinct reasons.
Diagnose the mapping before another import#
Read the saved mapping beside the original headers and a few authorised row values. Make sure an email field receives an email column, a company field receives a company value and the real header row was recognised.
If a column called “Last Contact” contains “Email Sent” or “Call 4”, mapping it to email will not make those values addresses. Choose the actual work-email column. If the first person's details became column headings, correct the source's header row before choosing the file again.
Keep contact restrictions in force. A suppressed row is not repaired by changing its email, removing a restriction or selecting a different destination. Fix malformed source values deliberately; do not invent addresses from a person's name.
Use Import and check your contacts for the picker limits, field mapping, duplicate handling and destination review. Remove unnecessary private columns from the file before selection. Excluding a column from mapping does not strip it from a raw upload.
Review the destination and its effects#
Check whether the rows go to your contacts or a campaign. Campaign enrollment can lead to outreach when that campaign's current controls and readiness permit it. An import is not automatically a harmless preview.
Before a new submission, reconcile the earlier job and review the intended rows, mapping, destination and current campaign state. Applicable usage, permissions, suppression and review controls still apply. Changing the destination to get around a refusal can create unintended work.
If you need to prevent campaign work, review that campaign's own controls separately. Pausing a source does not pause a campaign or cancel a job already in flight.
Use Import it again deliberately#
Where Import it again is offered for a file import, the live flow opens the file wizard. Choose the intended source file again, review its current contents and rebuild the mapping and destination deliberately. Kite does not retain that uploaded file as an automatic replay source for this control.
Opening or cancelling the wizard does not submit another import. The final import confirmation is the action. Check its returned job and actual outcome afterwards rather than assuming the old import became successful.
For rows already written, decide whether another import should update them. For unresolved rows, make a deliberate correction. Do not submit the whole file repeatedly to find out whether the earlier result was complete.
The file wizard opens on source selection with Continue disabled; no file is selected or import submitted.
Use Read it now for a saved source#
Read it now checks the saved source using its saved mapping and destination. It can queue an import, including when scheduled checks are Off. Use it only when you intend that work.
Read the response. Queued means work is waiting, unchanged means this content check found no change to import, and already queued or running refers to existing work. A not-due result refers to a scheduled check that has not reached its due time. None of these is a completed-import receipt.
Then find the relevant job in Imports. If the request was unconfirmed, read the source and import list before pressing again. Preserve the error and the time so you can distinguish the existing job from any later one.
Pause or remove a source with the right expectation#
Use the source's On/Off control when you want to pause future scheduled checks, then read back the state. A queued or running import can still finish. A manual Read it now is a separate action.
Remove removes the saved source, not contacts already imported. Preserve the schedule details if you need them, review the confirmation and read the source list again after the action. An unavailable list cannot confirm removal.
For a refused Sheet read, check the saved link and its intended access. The direct route needs a sheet accessible to anyone with its link. Do not make a confidential sheet public to clear the error; use an appropriate supported file or authorised connected route instead.
For a provider grant or key problem, follow Recover provider connections. Reconnecting does not itself complete a previous import.
A refused Sheet record shows a stopped result, zero recorded writes and an unreported source row total.
Watch the recovery controls#
The walkthrough shows the import list, a partial import's mapping and counts, an unreadable source and the Syncing view. It stops before any import, re-read, schedule change or removal. Follow the written steps to diagnose your actual records.
Reconcile an import before repeating it
Work with your agent#
Ask for an import-recovery diagnosis from current authorised reads. Have the agent name the source, job, destination, observed counts and error, and keep absent information unknown. It should propose a correction and a readback checklist before any new import.
Some saved-source controls may only be available in the product. An agent should use the supported in-app handoff when its current connection lacks the necessary read or action. Campaign enrollment remains with the person in Kite; public University tools provide guidance rather than private account access.
A clear task to copy
Prepare an import-and-sync recovery diagnosis. Discover the currently available authorised Kite tools and their exact argument schemas before reading account state. Use only supported reads in the correct workspace. Keep missing fields, failed reads and partial results unknown. Cite the current University guide, stable section and version. Public University tools supply guidance and do not reveal private account state or grant permission to act. Find the original source and job, its destination, recorded state, written and skipped counts, mapping and error. Keep absent totals unknown and do not infer no writes from failed/stopped state. Compare authorised headers and values without reproducing private rows. Distinguish a saved source schedule from its import job, paused future reads from queued work, and unchanged/already-running/queued results from completion. Another file import requires selecting and reviewing the source again; Read it now can queue work using the saved destination. Removing a source retains imported contacts. Campaign enrollment remains with the person in Kite. Propose the smallest correction and current-state reconciliation before another request. Prepare only. Do not save settings, change permissions or credentials, connect or disconnect accounts, run provider tests, book or move or cancel meetings, approve requests, enroll people, import or re-read sources, pause or remove sources, replay deliveries, send messages, activate work or spend money. Return the exact in-app review location and a readback checklist for me.
This prepares guidance. Use the controls in your Kite workspace for account changes and starting work.
Before you move on#
You can identify the original job, explain what it actually wrote, name the unresolved rows or unknowns and state why the proposed next action fits. Keep an unconfirmed result for Get help with useful context instead of repeating work blindly.
Your readiness check
0 of 7 checked
Your experience should make the next step clearer.
About this guide and its sources
Sources used to write and check this guide.
- Targeting, lists and exclusionsChecked 2026-10-10
- Channels and connectionsChecked 2026-10-10
- Current connected Kite tool schemasChecked 2026-10-11
- Customer responsibilitiesChecked 2026-10-16
- Kite contact import controls and recorded outcomesChecked 2026-10-11
- Booking, provider and import recovery controlsChecked 2026-10-13