Tech Talks After Hours: Data Integration - General Options
On this episode of Tech Talks After Hours, two OneStream Data Integration Team experts, Martin Toma and Joakim Kulan, join Tom Linton to discuss the current landscape of data integration techniques and options available with OneStream. Which techniques are typically used when? How do I put together a good data integration team? How do I best partner with OneStream on my data integration needs? These questions and more will be discussed as well as setting the path for future in depth conversations on the various integration techniques!
Key Topics Covered
- Data integration landscape overview: OneStream supports four broad categories of integration — file-based, external, database, and API — with the right approach depending entirely on the customer's environment, source systems, and internal capabilities
- Two-way vs. one-way connectivity: most integration types support bidirectional data flow (pulling data in and pushing data out); the exception is REST API used by external tools like Power BI, which pulls data out of OneStream only
- Integration is use-case specific: there is no single best approach — the combination of source system, data volume, security requirements, and available expertise at the client determines which integration type is most appropriate
- The discovery conversation: every integration engagement begins with understanding what source data exists, who at the client knows the source system, and what connectivity options are realistically available — this conversation always drives the technical path forward
- When file-based wins: even when clients have appetite for API or database connectivity, many implementations default to FTP or file-based integration because the client lacks internal expertise for more complex approaches; simpler is often more sustainable
- Evolution of integration technology: from early Upstream days where VB scripts were written to facilitate integrations, through to modern connectors and cloud-native options — the space has evolved significantly and continues to change rapidly
- OneStream's integration heritage: Tom Shea's work developing Upstream, which evolved into later products and ultimately into current OneStream integration capabilities, represents deep institutional knowledge that the consulting team draws on
- Database connectivity via .NET drivers: virtually any database can be connected to via the Microsoft .NET stack — panelists have rarely if ever encountered a database (outside of highly obscure legacy systems) for which a compatible driver did not exist
- Cloud data sources like Snowflake: modern cloud databases are connectable; security concerns are the most common barrier, but clients should assess actual risk and requirements rather than letting perception rule out otherwise viable options
- Security considerations for data transfers: authentication, data-in-transit protection, and the broader security landscape around integrations continue to improve alongside evolving threats — the same way antivirus technology has continuously improved
- Practical guidance for evaluating options: implementers and administrators should not let complexity or perceived security risk prevent them from exploring integration options — the right move is to have an informed conversation, understand what the integration actually requires, and assess client appetite
- Ongoing evolution of the field: data integration capabilities are a growing and evolving area of expertise; what is possible today will expand, and staying current is an ongoing requirement for anyone working in this space
To receive OnePoints for watching this Tech Talk video, please visit the link below:
Tech Talks After Hours: Data Integration - General Options