Datafeeds & API

1:1 delivery into Salesforce, warehouses, and downstream SaaS

SWFI datafeeds are structured so people, accounts, assets, and managed AUM stay consistent across CRM, data warehouses, analytics tools, and reconciliation workflows.

Open MSCI delivery Compatibility JSON
People contract SWFI Contact ID

Stable person identifier across CSV, JSON, and client delivery.

Account contract SWFI Account ID

Stable company identifier for CRM and warehouse joins.

Linked export People ↔ Accounts

Join-ready file for Salesforce mapping and reconciliation.

Delivery CSV / JSON / ZIP

Immediate client handoff formats already available.

Delivery contract

What every downstream system gets

People

Contact rows

Live

SWFI Contact ID, Name, Email, Title, Phone, City, State, and managed AUM context.

Accounts

Company rows

Live

SWFI Account ID, canonical assets, managed AUM, and discrepancy states.

Join layer

Linked accounts

Live

People-to-account mapping for CRM sync, warehouse joins, and reconciliation.

Exceptions

Discrepancy fields

Live

Assets and managed-AUM mismatch states stay visible instead of being hidden.

MSCI

Why this retains the account

No remapping tax

SWFI Contact ID and SWFI Account ID stay consistent across search, export, and delivery.

Delivery, not screenshots

MSCI gets working files, linked joins, and a packaged handoff instead of a promise to clean it up later.

One contract for every downstream system

The same people-account model can feed Salesforce, Snowflake, analytics tools, and connected applications.