Treatment of cbsubs 'import' users.

Hi,

We are a NFP association with several thousand members over a number of membership categories (both paid and “no charge”). This is a new website using CB and CBSubs.

We loaded our existing members (paid and unpaid) into CB using CBJuice2, in CBSubs we setup Plans and then imported the member status using CBSubs Import. All appeared to be well, the imported members are present in CBSubs Subscriptions and have both expiry dates and PlanIDs set. We have also setup expiry and overdue notices in CBSubs Mailer and these work well.

We are now finding that, for members loaded via the CBSubs Import facility, processing is substantially limited and different from that provided for new (and test) members. For our “Import” members neither the CBSubs change of state messages (Plan > Presentation: Manual Renewal, Pending Renewal, Automatic Renewal, Expiration, and Cancellation); nor CBSubs > Plans > Integrations > CB Fields actions; nor Auto Actions triggered using the “OnCPayUserStateChange” trigger. Also, when a long term member (who has been loaded via CBSubs Import) renews, the Plan message delivered is that designed for a brand new registration rather than a renewal.

Have we missed something? How do we load (or reset) our existing members (loaded via "Import") and have them treated exactly as if they originally subscribed via CBSubs?

Regards, Robert

Reviewed the entire import chain and looks like it behaves no different than giving them a subscription from backend or CB Auto Actions using direct API to create the subscription. The import appears to fire triggers and integrations as well when status is A (active) or X (expired). Believe they're treated as new subscriptions and not upgrades. Is all your behavior configured for upgrades?

All plans involved are configured for upgrades (e.g. Plan > Pricing “Total number of occurrences” set to zero, etc.). During testing, short duration test plans worked perfectly based on CBSubs initial signup and then renewals, cancellations, auto actions etc .

CB Tools shows no problems with databases etc.

Can you provide some problem solving guidance? Are there any subscription reports or log files that help? What CBSubs MySQL tables are involved? What fields should we focus on for differences between “Import” members and members added via CBSubs?

It gives them a subscription the same as giving them one from backend in CB > User Management while editing them. It should've logged the imports within CBSubs > History Log, but beyond that I've no idea why it's not working for some of your plans unless it's an issue specifically with those plans and their configuration. Try creating a new plan with a longer duration while leaving everything else at defaults and see if importing to it works fine.