Migrate from Refersion

A code recorded in your affiliate tool and a code that works at checkout are two different things, and a migration is where that difference shows up. During the import Referly can create each affiliate's code on the connected store itself rather than only logging it, so a customer typing MAYA15 gets the discount and Maya gets the sale. It can also pull codes that already exist on the store instead of minting new ones, which is usually what you want when the codes are already in the wild.

• Create new codes on Shopify, Stripe, WooCommerce or Polar during the import
• Or import the codes already on your store and bind them to the right affiliate
• Percentage or flat discounts, generated from the CSV's own discount column

Automatic coupon generation is on Business and above. Coupon tracking itself is on every plan, including Startup.

Refersion tracks Shopify, BigCommerce, WooCommerce, Magento and a Stripe install, and for a pure store that is a good list. If you have added a subscription, a course, a membership or an app alongside the store, the program stops being one program. Referly tracks store orders and recurring subscriptions on the same roster, with the same commission plan and the same payout run.

• Shopify and Stripe both connect by OAuth, in a click each
• WooCommerce, Paddle, Chargebee and Polar alongside them
• One affiliate, paid from wherever the money actually arrives

The risk on a CSV migration is a bad column mapping, and it usually announces itself about an hour later. Every import is a job that records what it created, so you delete the job, tick the box that removes its records, and the program goes back to exactly where it was. Then you fix the mapping and run it again. This is the reason a CSV migration is not the gamble it sounds like.

• Pause and resume a running import
• Per-record errors, so a bad row is visible rather than silently dropped
• Delete the job with or without the records it created