Prismatic has introduced native large data sync for customer-facing integrations, bringing high-volume data movement into the same platform used for embedded integrations.
The feature is aimed at B2B software companies that often run customer-facing integrations on one system while relying on separate tools for bulk data transfers such as backfills, migrations and refreshes. It allows teams to build, deploy, monitor and manage those workloads through one platform rather than maintain separate synchronisation infrastructure.
The product is intended to address a shift in how software vendors use integrations. Instead of handling only event-based exchanges between applications, integration tools are increasingly expected to support onboarding tasks, historical data transfers, recurring bulk updates and larger data ingestion jobs tied to analytics and artificial intelligence features.
That change has added work for engineering teams, which often need to build custom orchestration layers or adopt standalone synchronisation products. Prismatic's latest release is designed to remove that split by extending its embedded integration platform to process larger volumes of customer data using the same operating model as its current integration tools.
Growing workloads
According to Prismatic, the software breaks large datasets into bounded units at the start of an execution and then queues them for processing. The approach is intended to reduce the need for developers to create pagination frameworks, manage continuation tokens or orchestrate multiple execution flows to move large volumes of data.
Customers can use the new function for initial customer onboarding, historical migrations, recurring bulk refreshes and ongoing high-volume synchronisation. Prismatic also positioned the update as a way for software companies to ingest larger sets of customer data for AI and retrieval-augmented generation, or RAG, applications.
Users can monitor progress, review successful and failed batches, and retry failed batches from a single execution view. Large data sync is available in Prismatic's code-native integrations, while support for low-code use and its Embedded Workflow Builder is due later.
For software suppliers selling into businesses, data movement is increasingly tied to product adoption, as customers expect connected systems to stay current from the start of an implementation. Bulk transfers during onboarding can be particularly difficult because they require moving large historical datasets before routine application-to-application updates can begin.
Prismatic's latest move reflects a broader effort by integration platform vendors to absorb work that has previously sat in adjacent data tooling categories, including ETL and synchronisation products. The argument is that software teams want fewer systems to operate as customers ask for broader integration outcomes, especially when AI features depend on complete and current datasets.
Tanner Burson, Chief Technology Officer at Prismatic, said the demands on customer-facing integrations have changed as software products become more data-driven.
"We're seeing customer-facing integrations evolve from transactional connections into the data foundation for modern software. Whether it's onboarding a new customer, powering AI features, or keeping systems continuously synchronized, the expectations keep growing," Burson said.
He said the release is meant to let teams handle those jobs without adding another layer of operational complexity.
"Large data sync extends the same platform our customers already use to build, deploy, and manage integrations, so they can meet those new demands without adding another layer of infrastructure," Burson said.
Prismatic describes itself as an embedded integration platform focused on B2B SaaS providers. Native large data sync is now available to customers as part of its platform.