Ga naar inhoud

Bringing In CRM Data

Deze inhoud is nog niet vertaald.

Chapter 4 of Data 360 Architect, Part 1: Bringing Data In. Previous: The Doors In.

Chapter 3 walked the doors in. This chapter goes through the one most projects open first: the Salesforce orgs a company already has. Single org, multi-org, the standard objects, and the whole flow of creating custom objects and bringing them in. Data 360 sits beside your org, but to Data 360, your org is a source like any other, with a connector built for it.

  • Your org is a source. The home org connects itself; other orgs are connected by hand, each with an alias that names every stream and can’t be changed.
  • Start fast, but read what you got. A standard data bundle builds the streams and the mappings; trace them right to left, and decide before you deploy.
  • In Data 360, there is no contact; there’s the individual.
  • Custom objects need core work first: a deployed object, and a connector that’s allowed to see it and its related objects.
  • Freshness is a business answer, and it costs credits. Batch, streaming or about a minute: pick the slowest the use case allows.

Four modules, each standing on its own.

  1. Your Orgs Are Sources Too (coming soon). The home org, other orgs, the alias, and what to prepare before you connect.
  2. Data Bundles: the Fast Start (coming soon). What a standard bundle maps for you, and what it leaves to you.
  3. Custom Objects: From Core to Data 360 (coming soon). The whole flow, from a custom object in core to its records in Data 360.
  4. How Fresh Is CRM Data? (coming soon). Incremental refreshes, batch or streaming, full refreshes, and Accelerated Data Ingest.
  • Which orgs and objects come in, and the alias for each org.
  • Who prepares each org: domains, API access, and the connector’s permissions.
  • Where each object starts: a standard bundle, or a stream of your own.
  • How fresh each object needs to be, and what that costs.

All checked 2026-11-01.

Next: Streams and the Lake