Importing SaaS Data into FSM Data Ingestion Utility: CSV File or API?
The FSM Data Ingestion Utility has a flexible workflow for ingesting SaaS vendor data via a CSV file and API. The following table explains which SaaS data ingestion method scenario may work best for your organization.
Scenario |
SaaS Data Ingestion Method |
||||||
The SaaS application has preconfigured settings for ingesting and processing SaaS usage data as documented in Preconfigured SaaS Applications Within the FSM Data Ingestion Utility. |
You can ingest your SaaS application data via API into FSM Data Ingestion Utility as described in the application’s README file. For a list of SaaS applications with preconfigured settings for ingesting and processing SaaS usage data, see the KB article Flexera SaaS Management Data Ingestion Utility. |
||||||
I can export all of my organization’s SaaS application data using a CSV file. |
You can ingest your SaaS application data via a CSV file into FSM Data Ingestion Utility as described in Scheduling CSV Jobs in FSM Data Ingestion Utility. |
||||||
The SaaS application vendor provides API to ingest all of my organization’s data. |
You can ingest your SaaS application data via API into FSM Data Ingestion Utility as described in Scheduling API Jobs in FSM Data Ingestion Utility. |
||||||
The SaaS application vendor only provides API to ingest my organization’s user roster. |
Flexera recommends a two-part SaaS application data ingestion process.
|