
Celigo Sync: What It Does, What It Doesn't, and When It's Worth It
Category Celigo
Blog_field_Datum November 16, 2026
Your sales data lives in Salesforce. Your invoices sit in NetSuite. Your reporting team needs both.
Getting that information into one place, and keeping it up to date, is often more complicated than it sounds. Different systems have different data structures, update schedules and ways of accessing records.
Celigo Sync simplifies the data ingestion part of that challenge. It moves data from business applications into a data warehouse, where it can be prepared for reporting and analytics.
But what does it actually automate? What still needs to be built? And when does it make sense to use it?
What is Celigo Sync?
Celigo Sync is a data ingestion capability within the Celigo platform. It extracts data from applications and loads it into analytical destinations, including Snowflake, Google BigQuery, Amazon Redshift, Microsoft Fabric Warehouse and NetSuite Analytics Warehouse.
The architecture is straightforward:
Business applications Celigo Sync Data warehouse Analytics & reporting
Sync uses an Extract, Load, Transform (ELT) approach. Instead of applying all business logic before loading, it brings data into the warehouse in or close to its original form.
It supports lightweight preparation, including masking sensitive fields and handling nested data structures. More complex work, such as matching customers across systems, calculating financial KPIs or building dashboards, still happens downstream.
How is it different from a regular Celigo flow?
Traditional Celigo flows can also load data into a warehouse. However, building a separate flow for every dataset may require substantial configuration and ongoing maintenance.
Celigo Sync automates several of these steps.
It can discover source structures, create destination tables, map data types and apply rules when the source schema changes.
The benefit is less repetitive integration configuration, especially when multiple datasets need to be loaded and maintained.
It is important to understand the distinction: Sync is designed for analytical data ingestion, not to replace operational integrations that create orders, update inventory or execute business processes between applications.
How does Celigo Sync work?
The implementation consists of three main steps.
1. Connect and select your data
Start by connecting a supported source application and selecting the datasets you need.
For NetSuite, Celigo supports direct selection of saved searches, custom exports and a JDBC-based approach. The JDBC option requires a separate paid NetSuite SuiteAnalytics Connect subscription.
For Salesforce, you can select objects such as Accounts and Opportunities.
Rather than extracting everything, start with the data required for your reporting objectives.
2. Choose how records are loaded
Celigo provides two main extraction approaches:
All
Extract every available record during each run.
Delta
Extract records that were created or modified since the previous successful run, using the configured change-detection mechanism.
You also choose how those records enter the warehouse.
| Load method | What it does |
|---|---|
| Merge | Updates existing records and inserts new ones based on their primary keys. |
| Append | Adds new rows without checking for duplicates. |
| Replace | Replaces the destination table’s existing contents. |
For frequently updated transactional data, Merge combined with Delta can be an efficient choice. However, it requires suitable record identifiers and reliable change tracking.
These settings can be configured separately for different objects or exports.
3. Schedule and monitor
Celigo Sync can run manually or on a schedule, with standard intervals ranging up to every 15 minutes.
It also provides execution monitoring, error notifications and schema drift management.
For example, when a source application introduces a new field, the configured schema drift policy determines whether Celigo automatically adds the corresponding column to the destination.
Keep in mind that scheduled ingestion is not real-time synchronisation. Runs enter a processing queue, and the data becomes available according to processing and loading times.
Four things to consider before implementing Celigo Sync
Automation reduces repetitive work, but several technical decisions remain important.
1. Deleted records need special attention
Celigo provides a _celigo_deleted system column for soft-delete tracking. However, deletion behaviour depends on the source and extraction strategy. A full-refresh Merge can remove destination rows that no longer exist in the source, while incremental extraction may not detect a deletion without an appropriate source signal.
Test how your specific source handles deletions before relying on the warehouse data.
2. Primary keys determine data integrity
Merge depends on correctly identifying records.
If the selected key is not unique or stable, records may be duplicated or incorrectly updated. For custom exports, these identifiers must be configured explicitly.
3. Data can become available before a run finishes
Merge loads records in chunks, meaning reports may query data while a Sync is still processing.
If a run fails, previously loaded chunks remain in the destination.
For reporting that requires a consistent dataset, coordinate downstream processing with successful Sync completion.
4. Schema changes still require ownership
Celigo can detect structural changes, but not every change should automatically be accepted by your reporting model.
For example, when a source field is removed, its historical values can remain in the warehouse even though the field is no longer maintained.
Someone still needs to understand and manage the impact on downstream reports.
Example: Bringing NetSuite and Salesforce data together
Consider a company using Salesforce to manage opportunities and NetSuite to manage invoicing.
Management wants to understand how its sales pipeline compares with actual revenue across customers.
With Celigo Sync, the architecture could look like this:
Salesforce Celigo Sync Data warehouse
NetSuite Celigo Sync Same data warehouse
Each Sync connects one source application to one destination. Multiple datasets from the same source can be included within a Sync.
Once loaded, the warehouse contains the data needed to build the comparison.
But important questions remain.
- Do the customer identifiers match?
- How are different currencies handled?
- Which invoice statuses count towards revenue?
- Are credit notes included?
These decisions belong in the reporting model.
A successful data load confirms that records reached the destination. It does not automatically mean your business reports are accurate.
That is why data ingestion should be designed around the business questions it needs to support.
What does Celigo Sync cost?
Cost is an important part of the architecture decision.
As of November 2026, Celigo’s documented subscription allowances include one active Sync and the following monthly record volumes:
| Celigo edition | Included records per month |
|---|---|
| Standard | 500,000 |
| Professional | 2.5 million |
| Enterprise | 5 million |
Additional Sync capacity and record volumes may require add-ons. For example, the Salesforce and NetSuite scenario above uses two Syncs, so the available entitlement needs to be checked.
Importantly, Celigo counts records successfully loaded during each run, including updates to existing records.
Consider a warehouse table containing 200,000 records.
≈ 6 million
Reloading that entire table every day for 30 days consumes approximately 6 million records.
≈ 60,000
If only 2,000 records change daily, using Delta extraction could reduce subsequent monthly consumption to approximately 60,000 loaded records, assuming those changes are captured correctly.
The initial historical load, additional datasets and any subsequent full reloads must also be included in the estimate.
This makes extraction and scheduling decisions important not only for performance, but also for controlling costs.
For current entitlements and additional capacity, consult the Celigo platform editions documentation.
When is Celigo Sync worth considering?
Celigo Sync is particularly relevant when your organisation:
- Already uses Celigo and wants to extend its integration platform into analytical data ingestion.
- Needs recurring data loads from ERP, CRM or other business applications.
- Uses or plans to introduce a supported data warehouse.
- Wants to reduce the maintenance involved in configuring separate ingestion pipelines.
However, it is not automatically the best solution.
If your existing ingestion architecture works reliably, replacing it may offer little value. And if a reporting requirement can be handled within one application, a new warehouse pipeline may introduce unnecessary complexity.
The right decision depends on your existing architecture, data requirements, expected volumes and operational responsibilities.
How Teknuro can help
At Teknuro, we specialise in connecting business-critical systems, with extensive experience in Celigo, NetSuite and enterprise integration architecture.
For organisations considering Celigo Sync, we can support the full ingestion lifecycle.
- Assess the architecture. We review your existing applications, integration landscape, warehouse environment and reporting requirements to determine whether Celigo Sync is an appropriate fit.
- Design and implement. We configure source connections, extraction methods, destination schemas, primary keys, refresh schedules and appropriate security controls.
- Validate the data. We test updates, duplicates, deletions and data completeness, including reconciliation against the source systems where applicable.
- Monitor and optimise. We establish error monitoring, documentation and operational ownership, while reviewing performance and record consumption as requirements grow.
Where advanced warehouse modelling or dashboard development is required, we define those responsibilities separately with your data team or BI partner.
Our focus is not simply on transferring data. It is on building reliable integrations that support the outcomes your business needs.
Start with one business question
You do not need to move every available dataset into a warehouse on day one.
Start with a reporting question that matters. Identify the source data, agree on the refresh requirements and establish how the results will be validated.
Once that first use case works reliably, you have a stronger foundation for expanding your analytical capabilities.
Integration Quickscan
Considering Celigo Sync for your organisation?
Book an Integration Quickscan with Teknuro to review your existing architecture, assess the available integration options and identify a practical starting point.

