Step 2: Jobs

Jobs and transactions

Here is where we will be going over Jobs, and What jobs are for. We use jobs in conjunction with our custom built connectors and endpoints to connect, define, and move content from the source to destination. We have a few things to know before jumping in.

When a job is ran ImpulseSync will go through a few stages it will make sure it can connect pick up content from the source, place it in the content lakehouse and then transform the content so it can be put in the destination. That being said we do this through our mapping which we will learn in our step 2b. We also will learn how to use content manipulators in step 2a. We'll go over more in the steps of job configuration but this is the basis of how impusleSync can migrate your content over: 1. Connecting to the platform 2. Picking up content 3. Applying mapping and manipulators (if any) 4. Syncing content and delivering it to the destination.

We'll begin by learning how to set up these jobs to sync content over.