Answers.Body: <p>You are aware that stripe can interface directly with civi? it would save you the trouble to have to import.</p>
  
  <p>As for your question: not to my knowledge, but for your team, wouldn't it simple enough to do a search/replace in excel?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-25T14:33:00.443Z
Answers.Text: Yes, I am aware. There was a period when this was broken and so there's a month of data that needs to be imported manually. And yes, we could download the CSV, munge it manually, save it, and then save it, but that's an awfully tedious process to document.
Answers.UserDisplayName: Dave Rolsky
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-25T07:17:26.490Z
Answers.LastActivityDate: 2017-09-25T07:17:26.490Z
Answers.UserDisplayName: Xavier
Body: <p>Here's a specific example. When I export data from Stripe, there is a <code>Status</code> column with the value <code>Paid</code>. This obviously corresponds to CiviCRM's <code>Contribution Status</code> field. <strong>However</strong>, CiviCRM doesn't use the term <code>Paid</code>, it uses <code>Completed</code>.</p>
  
  <p>If I try to just directly import data from Stripe, CiviCRM complains about invalid status (and other fields with similar issues).</p>
  
  <p>I could easily write a little script to munge CSV files from Stripe into something that makes CiviCRM happy, but I really want to create a process that our staff without deep technical skills can use. Running a command line Perl script is out of the question. I could make a web app to munge the CSV files but now we're getting into very silly amounts of work for something absolutely trivial!</p>
  
  <p>Ideally, CiviCRM would have some sort of notion of munging/mapping for the <strong>values</strong> in the data being imported, as opposed to just mapping the field names.</p>
  
  <p>I didn't see any extensions along these lines but maybe I missed something.</p>
  
  <p>I'd love to learn how others have solved this problem.</p>
  
Tags: <civicontribute><import>
Title: How can I easily import data from external sources like Stripe while dealing with subtle differences in field values?
ThreadText: # How can I easily import data from external sources like Stripe while dealing with subtle differences in field values?
  
  (Asked by: username_0 on 2017-09-24)
  
  Here's a specific example. When I export data from Stripe, there is a `Status` column with the value `Paid`. This obviously corresponds to CiviCRM's `Contribution Status` field. **However**, CiviCRM doesn't use the term `Paid`, it uses `Completed`.
  
  If I try to just directly import data from Stripe, CiviCRM complains about invalid status (and other fields with similar issues).
  
  I could easily write a little script to munge CSV files from Stripe into something that makes CiviCRM happy, but I really want to create a process that our staff without deep technical skills can use. Running a command line Perl script is out of the question. I could make a web app to munge the CSV files but now we're getting into very silly amounts of work for something absolutely trivial!
  
  Ideally, CiviCRM would have some sort of notion of munging/mapping for the **values** in the data being imported, as opposed to just mapping the field names.
  
  I didn't see any extensions along these lines but maybe I missed something.
  
  I'd love to learn how others have solved this problem.
  
  **Tags:** civicontribute, import
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-09-25. Score: 1
  
  You are aware that stripe can interface directly with civi? it would save you the trouble to have to import.
  
  As for your question: not to my knowledge, but for your team, wouldn't it simple enough to do a search/replace in excel?
  
  > **Comments:**
  > **username_0**: Yes, I am aware. There was a period when this was broken and so there's a month of data that needs to be imported manually. And yes, we could download the CSV, munge it manually, save it, and then save it, but that's an awfully tedious process to document.  
  
  ---
  
  