Moving onto PartnerStack? Make a change on your integrations and need to backfill data? Or did a Partner request to be credited for a sale they made before they joined your program?
All of the above are reasons to import historical data into PartnerStack. Good news - it’s as easy as 1-2-3! First, figure out what you want to import. Is it Customer records? Transactions? Second, fill out the corresponding CSV (which you can find below in this guide). Third, send the CSV to your CSM and they will upload it for you!
Not sure who your CSM is? Reach out to Support@PartnerStack.com
Importing historical data can allow you to:
- Create Partnerships with a Partner (or Partners) that you work with
- Add Customers and connect them to a specific Partner
- Backfill historical transactions that Customers have made
- Reward your Partners for historical transactions - or just create manual rewards in bulk!
Each of these imports requires a different set of data to be imported - so let’s talk about what data we need for each type of import.
Quick links:
Partner Import
Customer Import
Transaction Import
Rewards Import
Partner Import
Migrating from another system or a homegrown solution? Importing Partners will create an account for all your Partners - so that all that will be left for them will be to claim their account and start referring you business!
Here are the fields and headers that we need to import Partners:
Mandatory
- Partner_first (The Partner’s first name)
- Partner_last (The Partner’s last name)
- Partner_email (The Partner’s email address)
Optional
- partner_key (This is a unique identifier for the Partner. If none is provided, we will create a randomized partner key for them. This will be what populates at the end of a Partner’s default referral link)
- Partner_group (Which group would you like the Partner to go into? If none is provided, we will place the Partner in the Default group)
- Partner_joined_date (This is the date that the Partner signed up to your Partner Program. If none is provided, we will use the date of import)
Customer Import
Has a Partner requested to have a previous referral they made attributed to their account? Did they send the referral manually via phone or email? Importing Customers will create a Customer record and attach it to a Partner profile so that the Customer’s purchases will be tracked going forward and the Partner can receive the credit!
Here are the fields and headers that we need to import Customers:
Mandatory
- customer_id (The Customer Key - which is how PartnerStack tracks recurring purchases made by Customers. If you are unsure of what this is, we recommend looking at current Customer records from within PartnerStack. Typical values here are the Customer emails, or an Account ID that is synced with your billing system)
- email (The Customer’s email address. This can also be anonymized for protection of PII)**
- partner_key (The referring Partner’s partner_key. This can also be replaced with partner_email, being the Partner’s email address associated with their Partner account)
**Note: The Customer email address must be unique to import - so if a customer exists in PartnerStack with that email, that Customer will fail to import. We recommend calling out these records separately to your CSM so they can help get these records into PartnerStack.
Optional
- name (This is the Customer’s name. If none is provided, we will leave the name blank and display the Customer’s email instead)
- signup_date (This is the date that the Customer signed up for your product. If none is provided, we will use the date of import)
Transaction Import
Did a Partner request to get credit for a previous referral they made? Importing Transactions will create individual Transactions and attach them to a Customer record so that the Customer’s lifetime value is accurate - and can also generate rewards for Partners!
Here are the fields and headers that we need to import Transactions:
Mandatory
- customer_id (The Customer Key - which is how PartnerStack tracks recurring purchases made by Customers. If you are unsure of what this is, we recommend looking at current Customer records from within PartnerStack. Typical values here are the Customer emails, or an Account ID that is synced with your billing system)
- amount (This is the transaction amount in cents. Eg; $500 USD transaction? Enter 50000 as the amount)
Optional
- transaction_id (While this is optional, we highly recommend including a transaction_id. This is used as a de-duplication mechanism, and is important for troubleshooting or reporting in the future. This can either be a unique value from your internal systems, or it can be made up)
- transaction_date (This is the date that the Customer actually paid you for your product. If none is provided, we will use the date of import)
- Product_key (Some companies have different reward structures for different products. If you have this set up, you can pass over the product_key that you would like us to import. If none is provided, we will leave this blank)
- Currency (This is the 3-digit currency code for the currency you would like us to upload the transaction in. If none is provided, we will default to USD)
Rewards Import
Want to reward Partners in bulk for a quarterly bonus? Or maybe just for being great Partners! Look no further - creating custom rewards via a Rewards Import is super simple.
Here are the fields and headers that we need to import Transactions:
Mandatory
- partner_key (This is a unique identifier for the Partner. If none is provided, we will create a randomized partner key for them. This will be what populates at the end of a Partner’s default referral link)
- reward_amount (This is the reward amount in cents. Eg; $200 USD reward? Enter 20000 as the amount)
- Reward_description (This is what your Partners will see as a reward description. You can get pretty descriptive here, but we recommend keeping it short and to the point)
Optional
- Reward_currency (This is the 3-digit currency code for the currency you would like us to upload the reward in. If none is provided, we will default to USD)