1С:CRM → Spreadsheets
AI-first ETL from 1С:CRM into Spreadsheets. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into Spreadsheets
Datrise syncs 1С:CRM's contacts, accounts, deals, activities, and lifecycle events into Spreadsheets as a tab per source entity. Flexible or custom fields land in JSON-stringified cells for nested fields, and timestamps such as created, updated, and status changes are typed as ISO-8601 text or serial date cells.
Sync is incremental: Datrise uses refreshes the tab's rows each run, preserving header order, so re-runs update only what changed. Sheets caps out around the low millions of cells, so Datrise lands a curated column set rather than every raw field.
Ideal for lightweight, shareable reporting for non-technical teams.
Endpoints
1С:CRM: CRM with strong adoption in CIS markets for sales and operations.
Spreadsheets: Business-friendly spreadsheet destination for collaborative analysis.
How 1С:CRM entities map to Spreadsheets
| 1С:CRM entity | Spreadsheets object | Notes |
|---|---|---|
| contacts | 1c_crm_contacts | id PK · custom fields → JSON-stringified cells for nested fields |
| accounts | 1c_crm_accounts | id PK · linked to 1c_crm_contacts |
| deals | 1c_crm_deals | id PK · linked to 1c_crm_contacts |
| activities | 1c_crm_activities | ISO-8601 text or serial date cells events |
FAQ
How does Datrise handle 1С:CRM's custom fields in Spreadsheets?
Flexible values are stored as JSON-stringified cells for nested fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Spreadsheets types.
How does the 1С:CRM to Spreadsheets sync stay up to date?
It runs incrementally — Datrise uses refreshes the tab's rows each run, preserving header order.
Related pipelines
More destinations for 1С:CRM
More sources for Spreadsheets
Early access
Connect 1С:CRM to Spreadsheets the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.