Best Practices | Recurly

Best Practices

Historical data

For auditing and technical reasons, Recurly cannot import historical data or backdate subscriptions. A CRM can be used to merge data from multiple systems for a full accounting profile.

Account Code Mapping

Show table of common unique IDs from known vendors (e.g. Stripe, Braintree, Authorize.net, Zuora).
Recurly will only import credit card data with an associated account code record, provided in the merchant mapping file. This is because many gateways have old, expired, or duplicate card records so Recurly will only import what we are specifically pointed towards importing.

Account billing level data

Since this process only manages sensitive billing information, only billing level data (e.g. card number, expiration date, card name, card address) will be populated. All other, less sensitive data, can be populated using the Recurly API without worry of PCI scope.

Timing and cutovers

Recurly strongly encourages a graduated import experience - start funneling new subscribers into Recurly while your legacy customers renew in your legacy platform - rather than a quick cutover.

Testing

After moving into production mode, all data is kept for historical auditing and accounting purposes, and Recurly fees are applicable. Recurly recommends keeping production test transactions to a minimum, and maintaining a second sandbox site for ongoing testing.