Skip to main content

Exporting from a Workspace Table

How to export a Workspace table to CSV, sync contacts to your CRM, or push them into an Engage sequence — including costs and scope options.

Written by Oscar Derderian, III
Updated today

Workspace tables support multiple export destinations: CSV files for offline use, direct CRM sync, and Engage sequences for outreach. This article explains each export option, what data is included, and the associated costs.

Selecting contacts for export

Before exporting, select the contacts you want to act on:

  • Select individual rows — Use the checkbox on the left of each row

  • Select all on page — Click the checkbox in the column header to select all visible rows on the current page

  • Export all rows — Available from the CSV export options (no selection needed)

Once contacts are selected, the export buttons in the toolbar become active.

Export Option 1: CSV

Click the CSV button in the toolbar. A dialog appears with three scope options:

Option

What it exports

Selected rows only

Only the rows you have checked

Current page

All rows visible on the current page

All rows (including filtered)

Every row in the table, applying any active filters

What's included in the CSV: The export includes every column visible in your table at the time of export — including all Lusha data and any enrichment data (AI Data, Signals, CRM fields) for which data has been run. Columns you have hidden from view will not be included.

Adjusting page size before exporting: If you want to export a "current page" of a specific size, change your Rows per page setting first (25, 50, 75, or 150) using the dropdown at the bottom of the table.

Shown vs. unshown contacts: The export dialog also lets you choose whether to include contacts whose details are still masked (unshown). If you include unshown contacts, you will be charged credits to reveal them during the export.

Cost: 1 credit per 25 rows exported

Legacy export format: If you need the simplified export format from classic Lusha lists (fewer columns), click the three dots (⋮) next to the table name and select the legacy export option.

Export Option 2: CRM sync

To push contacts directly to your connected CRM:

  1. Select the contacts you want to sync

  2. Click the CRM button in the toolbar

  3. Lusha syncs the selected records to your connected Salesforce or HubSpot account

Lusha maps contact fields to your CRM objects automatically based on your integration settings. For Salesforce, contacts are pushed as Contact or Lead records depending on your configuration. Read more on the Salesforce Integration article.

Cost: CRM sync does not consume additional credits beyond the original reveal cost.

Export Option 3: Sequences (Engage)

To push contacts directly into an Engage email sequence:

  1. Select the contacts you want to enroll

  2. Click the Sequence button in the toolbar

  3. A sidebar opens — select the active sequence you want to add them to

  4. Confirm the selection

The contacts will appear in that sequence in Engage, ready for outreach.

Requirement: You must have at least one active Engage sequence set up before using this option.

Key differences from classic list exports

If you're familiar with exporting from Lusha's classic lists, note the following changes in Workspace:

Classic lists export

Workspace table export

Fixed set of standard columns

All visible columns exported, including enrichment data

No enrichment data in export

AI Data, Signals, and CRM column values are included

Tags could be exported

Tags are not supported in Workspace; use filters instead

Legacy format only

New format default; legacy format available via ⋮ menu

FAQs

Can I export company data from a company table?

Yes. Select company rows and use the CSV export. Company tables export the company-level data columns visible in your table.

What happens to hidden enrichment columns?

Columns you have removed from your table view will not appear in the CSV export. Make sure all columns you want to export are visible before downloading.

Is there a row limit for CSV exports?

There is no hard limit on rows per export, but very large exports (thousands of rows) may take a moment to generate.

Did this answer your question?