Preparing for a Historical Sync in SyncSmart: NetSuite → HubSpot

Last updated: November 2, 2026

Before starting a historical sync, make sure your NetSuite environment and saved searches are prepared. The configuration of your saved searches directly affects the accuracy of the data that SyncSmart processes.

Overview

A historical sync processes existing NetSuite records (for example, Companies, Contacts, Items) and pushes them to HubSpot. The sync uses NetSuite saved searches to identify which records to include.

Requirements for Saved Searches

  1. Create a saved search for each object type. Provide a saved search for each object you want included in the historical sync, such as Companies, Contacts, or Items.

  2. Make the saved search public. Set the saved search to Public so the integration role can access and process the search results during the sync.

  3. Include only the required fields. Each saved search should include only two columns:

    • Internal ID: the unique key used to identify and sync each record.

    • Record identifier: such as the Company Name, Contact Name, or Item Name (used for readability and logging).

  4. Order by Internal ID. Sort the saved search results by Internal ID (ascending) so records are processed in a predictable, sequential order.

How SyncSmart Uses the Saved Search

During the historical sync, each record in the saved search is processed using its Internal ID as the unique key. The integration then syncs all mapped fields defined in SmartHub (hub.syncsmart.io) for that object type.

Each record is created or updated in HubSpot based on the configured sync direction and your field mappings.

Example

Internal ID

Company Name

1234

SyncSmart Systems

1235

Lynton Integration

1236

Example Company

In this example, the historical sync processes IDs 1234 through 1236 and syncs their data into HubSpot according to your mapping configuration.

Submitting Saved Searches to SyncSmart

Once your saved searches are complete and verified, send the details to SyncSmart support. Include:

  • The saved search name and its internal ID (found at the end of the NetSuite URL when viewing the search, ex. savedsearch2058).

  • The object type (for example, Company, Contact, Item).

  • Confirmation that the search is public and ordered by internal ID.

SyncSmart support will then review the configuration and schedule your historical sync.

Summary Checklist

Before submitting your saved searches:

  • One saved search per object type (Company, Contact, Item, etc.)

  • Saved search is Public

  • Columns: Internal ID and Record Identifier

  • Results ordered by Internal ID (ascending)

  • Records accurately represent the data you want to sync