codex - 💡(How to fix) Fix Add bulk export for CRM contacts and list members to CSV, with optional vCard export [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17156Fetched 2026-04-09 08:01:49
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
closed ×1commented ×1labeled ×1
RAW_BUFFERClick to expand / collapse

Problem

There is no bulk export path for CRM contacts or contact-list members, and no way to export selected contacts as vCards. This makes migration, backup, and downstream sync workflows harder than they need to be.

Requested behavior

Add bulk export for:

  • CRM contacts to CSV
  • Contact-list members to CSV
  • Selected contacts to vCard (.vcf) as an optional export path

Scope

  • Support exporting all contacts, filtered subsets, and explicit multi-select where that already exists in the product
  • Preserve stable identifiers in CSV so exports can be re-imported or diffed
  • Include common contact fields such as name, email, phone, company, title, tags, owner, and timestamps where available
  • For contact-list member export, include both the list identifier/name and the member contact identifier
  • For vCard export, support multi-contact export for the current selection and generate a standards-compliant .vcf

Open questions

  • Should CSV export flatten multi-value fields into delimited columns, or emit repeated columns like email_1, email_2?
  • Should list-member export include denormalized contact data, or stay relational and emit only membership rows?
  • Should vCard export be available only for explicit selection, or also for filtered result sets?

Acceptance criteria

  • Users can export contacts to CSV from the main contacts view
  • Users can export contact-list members to CSV from a list view
  • Users can export selected contacts to a .vcf file
  • Exported files open cleanly in Excel/Google Sheets and standard contacts apps
  • Export handles empty fields, commas, quotes, and multi-line values correctly

extent analysis

TL;DR

Implementing bulk export features for CRM contacts and contact-list members to CSV and selected contacts to vCard will require adding new export paths and handling various data formatting considerations.

Guidance

  • Identify the required contact fields to be included in the CSV export, such as name, email, phone, company, title, tags, owner, and timestamps, to ensure all necessary information is preserved.
  • Determine the best approach for handling multi-value fields in CSV export, such as flattening into delimited columns or emitting repeated columns, to ensure compatibility with various spreadsheet software.
  • Develop a standards-compliant vCard export feature that supports multi-contact export for the current selection, considering the nuances of vCard formatting and compatibility with different contacts apps.
  • Consider implementing a flexible export system that can handle various filtering and selection options, including explicit multi-select and filtered subsets, to provide users with a robust export experience.

Example

No specific code example can be provided without more context, but a potential approach might involve creating a modular export system with separate functions for handling different export formats (e.g., CSV, vCard) and data sources (e.g., contacts, contact-list members).

Notes

The implementation details will depend on the specific requirements and constraints of the project, including the technology stack, existing data models, and user interface considerations. Careful consideration of the open questions and acceptance criteria will be necessary to ensure a successful implementation.

Recommendation

Apply a workaround by prioritizing the development of a bulk export feature for CRM contacts to CSV, as this will likely have the greatest impact on migration, backup, and downstream sync workflows, and then iteratively add support for other export formats and features.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING