Understanding StarfishETL Terminology

Whether you’re working with data in the cloud, on-premises, or in a hybrid environment, it’s important to understand the functions of StarfishETL and how they relate to your data project. Here’s a reference of some key StarfishETL terminology.


Connections are the link between two applications or databases that allows the flow of data. Connections typically use APIs to facilitate the exchange of information.


A connector is a product API that is translated to a native StarfishETL API. More than 20 years of integration experience stands behind our library of 400+ StarfishETL connectors for CRM, ERP, marketing automation, data repositories, and other applications.


Maps are the blueprints that outline where data should move from one application to another. StarfishETL can generate starter templates to reduce the manual mapping necessary to move data. This can reduce up to 70% of the work related to data mapping. Common transformations are built into StarfishETL, allowing you to transform your data from a dropdown list.


A job is a specific process within your integration workflow that maps data from one object to another. For example, the process of synchronizing data.


A project is a collection of jobs. It encompasses all the actions and activities related to a connection in StarfishETL. If you are integrating a CRM and ERP for example, the jobs, scheduling, scripting, notifications, and mapping would all be part of your project.


When a common transformation isn’t available, StarfishETL users can apply C#, Python, VBScript, or JavaScript scripting languages to map the data.

Monitoring & Notifications

Monitoring and notification tools trigger workflows, generate activities, alert team members, and flag issues.