Skip to content

Bring spreadsheet records into the right client report

An Excel workbook, CSV export and Google Sheet can all contain useful reporting records. First decide whether you have individual leads or monthly summaries. That choice determines the import path, the fields you can report and how you check the result.

Choose the job before choosing the file.

Adding client companies, importing their historical leads and publishing a spreadsheet report are different jobs. A client roster creates the account context; it is not a report of campaign performance. Monthly summaries cannot reconstruct individual leads or their original identifiers.

  • Use a client-list import when the rows describe client companies.
  • Use the historical-lead path when each row represents an original enquiry that needs review in the intended workspace.
  • Use spreadsheet reporting for a separate report from lead-level records or monthly summaries. Imported report totals remain separate from native lead and CRM totals.

Prepare a clear table of calculated values.

Keep one header row and one consistent record type in the selected table. A lead-level table needs identifiable lead records, dates and the source fields available in the original export. A summary table should make its period and metric definitions explicit.

  • Use stable identifiers, consistent date formats and separate amount and currency columns.
  • Check formula results in the source workbook before import. Attrival reads calculated results; formulas, formatting and Apps Script automations stay in the spreadsheet.
  • Keep contracts, collected payments and advertising conversion values in separately named fields. A column called revenue is ambiguous until its meaning is agreed.

Map fields rather than relying on the column order.

Match source headers to the destination fields and inspect the preview before saving. For example, a source column called Enquiry created should map to the lead submission date only if that is what it records. Deal closed is a different date.

  • Check that source and campaign are mapped separately, and keep unavailable attribution unknown.
  • Review outcome mappings against your client’s definitions. Appointment booked does not automatically mean won.
  • Inspect dates, decimal separators and currencies in the preview. A correctly uploaded file can still contain an incorrect field mapping.

Review duplicates and reconcile the same scope.

Count the source rows you intended to import, then compare the reviewed result. Explain skipped duplicates, rejected records and date exclusions before comparing totals. A smaller imported count can be correct if repeated records were deliberately excluded.

  • A lead appearing in two exports should not become two new leads simply because the files differ.
  • Compare the same client, record type, date period, outcome definition and currency.
  • If a monthly summary reports jobs closed in September, do not compare it directly with a native September submission cohort. The groups answer different questions.

Treat Google access and refresh as separate checks.

Google sign-in identifies a user; it does not authorize every spreadsheet. A Google Sheets source requires an authorized Google connection and permission to read the file an administrator selects.

  • Excel or CSV upload provides a reviewed snapshot without requiring a live spreadsheet connection.
  • Do not call an upload a continuous sync. Changes in the source require another import or an explicitly authorized refresh path.
  • A successful authorization screen is not proof that the intended rows reached the correct client report. Check the resulting records and scope.

Move a shared outcome sheet into the workspace.

If you keep a sheet per client and ask them to fill in what happened to each lead, those rows are worth keeping, and nobody has to retype them. Bring the history in once, then let the CRM take over the updates.

  • Import the past rows as historical leads and map the sheet’s status column to Attrival’s stages, such as Won, Lost or No response.
  • From the switch-over date, send new leads through Attrival so each one keeps its source and an Attrival Lead ID; its record in the client’s CRM is then found by that ID or by the customer’s email, phone or name.
  • After the client’s CRM is linked and its stages mapped, new outcomes arrive without anyone opening the sheet.
  • An authorized selected Google Sheet can refresh automatically. Excel and CSV uploads remain reviewed snapshots.

Check the report before inviting the client.

Open the resulting report, select the intended period and reconcile representative rows against the source. Check a won record, an open record, an unknown outcome and any excluded or duplicate record that changed the totals.

  • Confirm the destination workspace and currency-separated totals before sharing.
  • Keep imported spreadsheet totals separate from native leads and CRM totals unless you have explicitly reconciled the records. Otherwise the same lead may be counted twice.
  • Invite an authorized reader to the intended workspace. Imported history does not trigger follow-up messages or establish a working CRM delivery connection.

Turn your spreadsheet into a client report.