Review, resume and safely undo a CSV import

Use Imports → CSV migration to bring client, vendor, guest, gift or task records into your workspace. Each batch imports one record type. Guests, gifts and tasks need a selected wedding. The current importer does not recreate another CRM's conversations, signed documents, invoice history or pipeline stages.

Map a small sample first

Choose a CSV under 1 MB with at most 1,000 data rows and 60 columns. Use unique, nonempty column headings. Quoted commas, line breaks and Unicode text are supported; a single cell can contain at most 12,000 characters. Spreadsheet formula text is preserved as text and is not evaluated.

Map each source column to one supported destination field. Preview before importing. For example, map First partner to partnerOneName, Second partner to partnerTwoName and Email address to email. Check the displayed names, email addresses and row errors against the original export.

The preview creates an import record without adding contacts or changing existing work. Possible duplicates and invalid rows are skipped. Duplicate detection uses the available name, email or household fields for that record type; it is a review aid, not a guarantee that two people with similar names are the same person. There is no automatic merge. Correct a skipped row in the source and preview a new small batch when necessary.

Start, pause and resume

For guest imports, Keep household labels only preserves the spreadsheet labels without creating invitation links. Choose Create new household invitation groups when you want each group to answer together. Review the group preview before starting: identical trimmed labels are grouped within this file only, and capitalization matters. Blank labels create separate individual households. A group can contain at most 30 guests; use labels of at most 120 characters. Correct invalid or mistaken groups in the original CSV and create a fresh preview.

For example, Rowan and Jules with the label River family become one new household. Emery with a blank label gets a separate household. An existing River family household is never adopted, renamed or merged. Possible duplicate guests are skipped, so inspect the actual names shown in each group before proceeding.

Imported households start with inactive, unissued links and no plus-one allowance. Once the entire batch completes, use Choose invited events to review each guest's permissions, then Issue household links to create a private link under Household invitation links. Copy the generated link to the intended household. This importer never sends a message. Link issuance is blocked while that batch is importing, paused, undoing or paused during undo; finish or undo the batch first.

Gift values use integer cents: 12500 means $125.00 with currency USD. Use YYYY-MM-DD for received dates. Optional household IDs must already belong to the selected wedding. Gift imports create unsent thank-you records; they never send messages or mark a thank-you as complete. Matching giver, description, amount, currency and received date is flagged as a possible duplicate for review.

Approve the reviewed rows to begin. Work runs in bounded durable batches, so refresh the page for current progress. Pausing stops further batches; rows already added remain available. Resuming continues from the next pending row. Retrying the same preview request does not create a second batch.

Undo without erasing later work

Undo considers only records created by that import. It removes an unchanged record only when it has not acquired linked work. A client with a wedding, a guest with an event response, room allocation, transport reservation or recorded support need, a vendor used in a timeline or expense, and records referenced by current or saved layout versions remain for manual review. A gift edited or marked thanked after import is preserved too.

For grouped guest imports, undo also removes an empty, unchanged household that this batch created. Issuing or replacing its link, editing the household, adding a guest outside this import, or linking gifts, stays, posts or media preserves it and its remaining imported guests. Existing households are never removed by an import. Keep used household invitations and reconcile them manually if the source spreadsheet was wrong.

If someone edits an imported record, that record is preserved too. Partial undo means some records were deliberately kept; read each row's explanation. An interrupted undo resumes as undo and never switches back to adding the unimported rows. Keep the original export until you have checked the completed batch and any preserved records.

Move an inquiry pipeline

Choose LEAD to bring inquiry names, contact details, event date, venue, guest count, integer-cent budgets, messages, private notes, attribution, tags and stage. The importer suggests only unambiguous heading matches; review each mapping and the visible unmapped columns. Download the sample CSV to check the expected format. Semicolons separate tags. A budget in dollars is never silently treated as cents.

Custom stages map by the exact existing pipeline and stage names inside your business. Create those stages first, map both names, and review the preview. Missing or ambiguous stages hold that row. Possible duplicates are skipped without merging. Imports do not grant messaging consent, send messages or start workflows. The full original row remains in import history; unmapped columns do not populate the new record.

Undo archives unchanged imported inquiries with an explicit import reason, retaining their histories. Changed inquiries remain for manual review. Contact and inquiry imports do not manufacture signed agreements, received payments, message history or standalone event records from unavailable source data.