Fast2 comes with off-the-shelf tasks dedicated to the communication between the ECMs involved in the migration and the ETL itself. If the connector aims to retrieve data and contents from a storage infrastructure, it is then qualified as “extractor”. Otherwise, if its role is to be the bridge to load data into the destination system, Fast2 identifies it as an “injector”.
Needless to say that connectors are necessary for every migration since they are most of the time the opening and closing steps of the workflow. A lot of ECMs are supported by Fast2, you should easily find the one your are looking for down below. However, in case yours is not in this list yet, you might consider to build your own.