Answers.Body: <p>Depends on how you define non-manual. Only non-technical I know of is</p>
  
  <ol>
  <li><p>import just the cid, add to group as part of import, then export</p></li>
  <li><p>do a vlookup, and get your new data and old data for those fields on same spreadsheet</p></li>
  <li><p>use CONCATENATE to combine your new 'option values' with the existing 'option values'</p></li>
  <li><p>do import</p></li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-02T19:19:54.453Z
Answers.Text: Thanks for the help thinking it through, I will consider this!
Answers.UserDisplayName: Lisa J
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-28T19:33:28.360Z
Answers.LastActivityDate: 2017-03-28T19:33:28.360Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>If you are doing that regularly, you could write an extension to upload your csv, fetch the current values, merge in the new data and then update the contact.  </p>
  
  <p>Creating the extension is technical but it should be easy for non-technical users to run it.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-02T19:20:13.413Z
Answers.Text: Also a good idea, I will look into this, thanks for the help!
Answers.UserDisplayName: Lisa J
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-29T09:16:55.730Z
Answers.LastActivityDate: 2017-03-29T09:16:55.730Z
Answers.UserDisplayName: Aidan
Body: <p>My use case involves lots of importing, and extensive use of multiselect fields (to track things like skills, interests, etc). Sometimes we get new information about, for instance, an existing contact's skills. We want to include this new info in our import. But of course importing with "fill" overwrites the old information. We want to keep the old information and add the new information to it. </p>
  
  <p>Unfortunately this is not something we thought about when we designed our fields and processes!</p>
  
  <p>I am looking for advice on a (non-manual) process that a non-technical user could do to achieve the intended outcome (appending additional values to multiselect fields).</p>
  
  <p>If anyone has any experience with this I would much appreciate your insight.</p>
  
Tags: <import>
Title: Is there a way to preserve existing data when importing into multiselect and checkbox fields?
ThreadText: # Is there a way to preserve existing data when importing into multiselect and checkbox fields?
  
  (Asked by: username_0 on 2017-03-28)
  
  My use case involves lots of importing, and extensive use of multiselect fields (to track things like skills, interests, etc). Sometimes we get new information about, for instance, an existing contact's skills. We want to include this new info in our import. But of course importing with "fill" overwrites the old information. We want to keep the old information and add the new information to it.
  
  Unfortunately this is not something we thought about when we designed our fields and processes!
  
  I am looking for advice on a (non-manual) process that a non-technical user could do to achieve the intended outcome (appending additional values to multiselect fields).
  
  If anyone has any experience with this I would much appreciate your insight.
  
  **Tags:** import
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-03-28. Score: 2
  
  Depends on how you define non-manual. Only non-technical I know of is
  
  1. import just the cid, add to group as part of import, then export
  2. do a vlookup, and get your new data and old data for those fields on same spreadsheet
  3. use CONCATENATE to combine your new 'option values' with the existing 'option values'
  4. do import
  
  > **Comments:**
  > **username_0**: Thanks for the help thinking it through, I will consider this!  
  
  ---
  
  ### Answer by username_2 on 2017-03-29. Score: 0
  
  If you are doing that regularly, you could write an extension to upload your csv, fetch the current values, merge in the new data and then update the contact.
  
  Creating the extension is technical but it should be easy for non-technical users to run it.
  
  > **Comments:**
  > **username_0**: Also a good idea, I will look into this, thanks for the help!  
  
  ---
  
  