tag:support.getcheddar.com,2009-06-01:/discussions/questions/372-how-much-work-to-migrate-from-chargifyCheddar: Discussion 2022-01-10T20:37:03Ztag:support.getcheddar.com,2009-06-01:Comment/33345272010-10-13T04:51:47Z2010-10-13T04:51:48ZHow much work to migrate from Chargify<div><p>Based on the events of the last couple of days, I have a simple question... if we are integrated with Chargify today, what pains are we looking at to move to you guys? I am not so concerned about API integration (since we can control that and write new code) but what about our current customers? If their information is already stored in Authorize.net CIM, will we need to force them to re-enter credit card information? Are there any other MAJOR buriers (major meaning significantly painfully or customer experience-impacting) you are aware of in migrating?</p>
<p>We are basically now aware we need to have alternative strategies, regardless if the principal matters of the current changes force us to move or not and would like to know if we could viably migrate to you guys. Thanks.</p></div>Migration from Chargifytag:support.getcheddar.com,2009-06-01:Comment/33345272010-10-13T04:52:58Z2010-10-13T04:52:59ZHow much work to migrate from Chargify<div><p>Mis-entered name field on previous submission. Apologies.</p></div>Dan Zittingtag:support.getcheddar.com,2009-06-01:Comment/33345272010-10-13T15:51:38Z2010-10-13T15:51:38ZHow much work to migrate from Chargify<div><p>Hey Dan -- I'm not intimately familiar with the Chargify API so there's one thing to work out. Each customer has at least two CIM tokens associated with them. One for the customer's basic information and one for the customer's credit card information. Authnet calls them <em>customerProfileId</em> and <em>customerPaymentProfileId</em>. A customer can have more than one <em>customerPaymentProfileId</em> but CheddarGetter is only concerned with one (the one that pays the subscription). So, the question is, does the Chargify API let you pull these CIM tokens for each customer? I see that the API response has a field called <em>customer_vault_token</em> but there should be two tokens. If so, I don't see any problem with the migration. Your customers wouldn't even need to enter their card data again.</p>
<p>Can you send an example of a full raw API response for one of your paying customers? If so, let's start a new private thread with that information.</p>
<p>We're happy to help in any way we can. Please let us know if you have further questions!</p></div>Marc Guyertag:support.getcheddar.com,2009-06-01:Comment/33345272010-10-15T17:20:05Z2010-10-15T17:20:05ZHow much work to migrate from Chargify<div><p>Dan -- Were you able to determine if you can pull the tokens from the Chargify API? If not, we can use the Authorize.Net data directly. Either way, we can get it done.</p></div>Marc Guyer