Marketo to Redshift Migration: 2 Easy Methods

Most modern businesses now rely on Digital Marketing Tools to market their products, automate the implementation of their marketing strategies, measure the performance of their efforts using marketing reports and manage their Leads.

One of the most well-known Marketing Tools is Marketo. Marketo offers various features such as Marketing Automation, Email Marketing, Revenue Attribution, and Lead Management. Although Marketo is widely used by a large number of businesses, its analytical capabilities are limited. This article will provide you with an in-depth understanding of how you can migrate your Leads data from Marketo to Redshift to perform a comprehensive analysis of it and derive useful insights from it.

Methods to Set up Marketo to Redshift Migration

Users can set up Marketo to Redshift Migration by implementing one of the following methods:

• Method 1: Manual Marketo to Redshift Migration
• Method 2: Marketo to Redshift Migration Using Hevo Data

Method 1: Manual Marketo to Redshift Migration

Here are the basic building blocks of implementing a custom code to transfer data from Marketo to Redshift:

• Step 1: Creating Access Token for Marketo API
• Step 2: Extract Leads Data using Marketo API
• Step 3: Transforming JSON Data to CSV
• Step 4: Loading the CSV Data to Redshift

Step 1: Creating Access Token for Marketo API

• Login to your Marketo account and open the Admin page.

• Open the Users & Roles section from the left panel and click on New Role.

• Give a suitable name and description for the role and expand the Access API section.

• Scroll down and select Read-only Lead or any other access control option based on your requirements.

• You will now need to create an API-only user and associate it with the API role that was created previously. Once the required information about the user has been created, click Invite.

• A custom service would also be required to uniquely identify the client application. You can create a custom application by clicking on New Service in the Launchpoint section of Admin settings.

• Provide a name, service, and description based on your requirements. For the API Only User, select the user that was created previously.

• Now click on View Details next to the service that was created in the last step.

• You will not be able to see your Client Id and Client Secret that can be used by your client applications or to generate an access token.
• Click on GET TOKEN and copy the generated authentication string in a secure location.

• Copy this Token and save it in a secure location.

Step 2: Extract Leads Data using Marketo API

You can extract the Lead details from Marketo in JSON form using the Access Token generated previously by executing the following command:

curl -o marketo_leads.json <Identity URL>/rest/v1/leads.json?access_token=<Access Token>

The result will be a JSON structure as below.

{
    "requestId":"c493#1511ca2b184",
    "result":[
       {
           "id":1,
           "updatedAt":"2019-08-24T20:17:23Z",
           "lastName":"Tresco",
           "email":"marcus@marcusmaterials.com",
           "createdAt":"2013-02-19T23:17:04Z",
           "firstName":"Marcus"
        },
       {
           "id":2,
           "updatedAt":"2019-08-24T20:17:23Z",
           "lastName":"Elene",
           "email":"elene@marketo.com",
           "createdAt":"2013-02-19T23:17:04Z",
           "firstName":"Mercury"
        },
       {
           "id":3,
           "updatedAt":"2019-08-24T20:17:23Z",
           "lastName":"Arthur",
           "email":"arthura@iplusnetwork.com",
           "createdAt":"2013-02-19T23:17:04Z",
           "firstName":"Arnage"
        }
    ],
    "success":true
}

Marketo can return a maximum of 300 results per request. If the results consist of more than this number of entries, the API response will contain two additional parameters, i.e., moreResults and nextPageToken. The latter can be used along with the next request to fetch the next batch.

Step 3: Transforming JSON Data to CSV

Unfortunately, Amazon Redshift does not have native support for JSON so, for simplicity’s sake, you can convert the JSON output to a CSV file. Luckily, there are a number of tools available that can make this possible. One of the most widely used tools can be accessed here.

The CSV data can then be copied and saved in a file in your local system.

Step 4: Loading the CSV Data to Redshift

Users can load their data exported from Marketo to Redshift by implementing the following steps:

• Sign in to the AWS Management Console.
• Open the Amazon S3 Console and click on Create Bucket.

• Pick a suitable unique name for your AWS S3 Bucket, select a region as per requirement, and click on Create.

• Open the AWS S3 Bucket that you just created, click on Create Folder, provide a suitable unique name for it, and click on Save.

• Upload the LinkedIn Ads data exported previously to the newly created folder by clicking on Upload selecting the necessary files in the Upload Wizard.
• The data in Amazon S3 can be imported into Amazon Redshift Cluster using the COPY Command.
• Connect to the Cluster using a SQL Workbench tool of your choice and run the following query:

COPY table_name 
FROM 's3://<your-bucket-name>/load/file_name.csv' 
credentials 'aws_access_key_id=<Your-Access-Key-ID>' 
CSV;

• If you wish to ignore the file header rows in the CSV files, then you may also specify that by running the following query:

COPY table_name 
FROM 's3://<your-bucket-name>/load/file_name.csv' 
credentials 'aws_access_key_id=<Your-Access-Key-ID>' 
CSV
IGNOREHEADER 1;

Your data should now be accessible and queriable in your Amazon Redshift database.

Limitations of Setting up Manual Marketo to Redshift Migration

The limitations of setting up manual Marketo to Redshift Migration are as follows:

• The Marketo API is paginated in case the result has more than 300 entries. So the application logic should be able to keep track of the nextPageToken parameter and dynamically forming the next request if required.
• The API is rate limited with a daily quota, a 20-second quota, and a concurrency quota. The application logic should have provisions to work with these limits and handle exceptions in case the quota exceeds.
• The manual approach is suited for a one-off load or a first-time load. In case of a real-time update or recurrent load operation, additional logic to handle deletes, updates, and duplicates must be implemented. The fact that Amazon Redshift does not enforce Primary Key constraints will make this even more difficult.
• If not provided with configuration files to specify data type mapping, Amazon Redshift will leverage its automatic data type mapping, which can result in corrupted data. So a simple COPY command as above may not be sufficient depending upon the data types involved.
• This approach needs access to an intermediate instance where the CSV and JSON files are stored before loading to Amazon S3 and Amazon Redshift. This is not always feasible for completely Software-as-a-Service (SaaS) based architectures.

Method 2: Marketo to Redshift Migration Using Hevo Data

Hevo helps you directly transfer data from Marketo and various other sources to Amazon Redshift, Business Intelligence tools, Data Warehouses, or a destination of your choice in a completely hassle-free & automated manner. Hevo is fully managed and completely automates the process of not only loading data from your desired source but also enriching the data and transforming it into an analysis-ready form without having to write a single line of code. Its fault-tolerant architecture ensures that the data is handled in a secure, consistent manner with zero data loss.

Sign up here for a 14-Day Free Trial!

Hevo takes care of all your data preprocessing needs required to set up Marketo to Redshift Migration and lets you focus on key business activities and draw a much powerful insight on how to generate more leads, retain customers, and take your business to new heights of profitability. It provides a consistent & reliable solution to manage data in real-time and always have analysis-ready data in your desired destination. 

The following steps can be implemented to set up Marketo to Redshift Migration using Hevo:

• Configure Source: Connect Hevo Data with Marketo by providing a unique name for your Pipeline, along with details about your Marketo client such as the Client ID, Endpoint, etc.

• Integrate Data: Complete Marketo to Redshift migration by providing information about your Amazon Redshift database and its credentials such as database name, username, and password, along with information about port number associated with your Amazon Redshift database. You’ll also need to need to provide the Schema name for your database, and its cluster, along with a unique name for your destination.

Conclusion

This article provided you with a step-by-step guide on how you can set up Marketo to Redshift Migration manually or using Hevo. However, there are certain limitations associated with the manual method. If those limitations are not a concern to your operations, then using it is the best option but if it is, then you should consider using automated Data Integration platforms like Hevo.

Visit our Website to Explore Hevo

Hevo helps you directly transfer data from 100+ sources of your choice to a Data Warehouse, Business Intelligence, or desired destination in a fully automated and secure manner without having to write the code. It will make your life easier and make data migration hassle-free. It is User-Friendly, Reliable, and Secure.

Want to take Hevo for a spin? Sign Up for a 14-day free trial and experience the feature-rich Hevo suite first hand. Details on Hevo’s pricing can be found here.