Do a search that finds all contacts (for example, Find Contacts and then search without entering anything), then select "All nnn contacts" and choose Export from the drop down menu. You can select all primary fields or specific fields to export.
You should note the exceptions for the contacts with dual residences and manually remove their secondary residence, and only keep their primary residence in the sheet. You can always create their secondary residence address within CiviCRM after the import wizard finishes as a non-primary address.
For State/Province names and Country name mismatches, you can ...
You can do a search (of any kind) and the resulting screen will have an Actions select menu. Select any or all of your contacts and then you can select the Export Contacts in the Actions menu. See https://docs.civicrm.org/user/en/4.6/common-workflows/exporting-your-contacts/
You can also run any number of reports and save the result as a CSV.
This Log Export extension "logs to a files within the ConfigandLog directory whenever an export happens, who performed it what columns involved and the relevant entity IDs"
There is a blog about it here
CiviCRM populates current employer based on what is stored in civicrm_contact.current_employer rather employee/employer of relationship. While adding employee/employer of relationship relationship the form provide is_current employee option, if ticked civicrm_contact.current_employer is stored with organization name and also same field is used in add/edit ...
CSV files aren't a single common format. For instance, in the US, fields are often separated by commas, but in Europe, often by semicommas. If you're importing, there should be an "import field separator" option (see screenshot).
Ultimately, there's not enough information in your question to help you. Others have made suggestions as to how to better ask ...
Some options to consider
sometimes if you save a csv in eg LibreOffice and then edit it again and resave it can be rejected by civicrm, in which case simply try opening your csv, copy all cells in to a new csv, then save and do not re-edit that file or try the below method
sometimes an Excel generated csv can be a problem, in which case perhaps try loading ...
First the available countries and states/provinces need to be defined in the Localization settings.
If you cannot do the SQL query, you can see the available values by creating an address manually and seeing the available values.
The import allows state abbreviations for at least the United States. (e.g. Arizona - AZ). I use the abbreviations when I do ...
How are you recording the enquiry? As an activity? If so, you could add a custom field "exported" (Yes/No field, default No), then search for exported=no, export, and update exported=yes.
There are various problem scenarios you might want to think about: eg if an export is lost after you generate it (eg email bounces), do you need to be able to reproduce ...
Without seeing some of the actual file that is being imported, it is hard to say for sure. But my guess is that birth date field is an actual date field? And if so, it needs to be formatted as a date and on the first import screen you have to tell Civi how it is imported.
The error file that you can click and download will give you more information, as it ...
It is a bit complicated. You will need to do at least 2 different imports, with external IDs. The CSVs for imports would look at this
first_name, last_name, extID
Jane, Doe, 1
first_name, last_name, extID, Spouse-extID
John, Doe, 2, 1
Take a look at CiviCRM 5.29.0 - import relationships
The issue was unrelated to the log error, which we will debug at a future time.
The problem was caused by my preferred use of a semicolon ";" as a delimiter instead of a comma ",". I frequently use the semicolon because clients frequently include commmas in names and addresses. Apparently this disambiguation was a problem for the CSV Import Helper.
I faced the same problem and double-checked date settings in Civi. All well.
My solution was to delete the "head" and "footer" rows from the csv file, marked yellow in this screenshot:
The result is a clean csv spreadsheet with 1 row for header and a rows for every transaction. This file was imported as aspected to CiviBanking.
API CSV Import extension uses Job Scheduler to import the records in Civi. The job scheduler breaks down the whole csv into small batches(also known as queue item) to import to avoid timeout issue, memory excess and various reasons.
'Number of Items' is used to define how many records you want to process in single single queue. If you specify 2000 than there ...
Those fields aren't available from reports as far as I can see, but you can get your csv from a search. You can get all records from a contact search and then export including the group and tag fields. Or if you only want to select the records with groups or tags set you can use Search Builder to select these using include contacts where group is not empty ...
CSV Import and Form Processor IS a powerful combo! Check out the advimportformprocessor extension.
Note that this combines the "advimport" extension rather than the CSV API GUI extension with Form Processor. It's overall better, but some work on advimport's rough edges would improve the UX.
Also note that Form Processor is pretty slow, so imports ...
What version of Civi are you using?
Under Events > Reports > Participant List, Mine shows "Export CSV" as an Action Option
Under Search > Find Participants, it just says "Export List", But when I export it I get a CSV file.
But even if you get a .xls or other Excel file you can always save it as a .csv in Excel. If you do not have Excel, then run it ...
Reports that provide a simple table are more amenable to export as CSV. The Event Income Detail has different sections to it which does not fit well for a CSV format - what column headings would you use?
Whether a report offers a CSV export option depends on the settings in the code. The Event Income Detail report is provided by CRM/Report/Form/Event/...