A customer export may contain thousands of rows yet fail to explain a deal's company, attachment location or important field changes. When leaving a CRM or changing implementers, request a package preserving agreed relationships and meanings. Inspect a meaningful sample instead of relying on row counts.
Start with a relationship worth preserving
In a fictional workwear supplier, one contact relates to two companies, a deal belongs to one of them, and a note and synthetic proposal are attached. The buyer wants this case transferred without guessing from similar names. No export occurred; the example defines what the recipient should understand.
Name included entities such as contacts, companies and deals, plus exclusions and reasons. Choose a sample containing a multiple association, changed value, activity and file. An uncomplicated customer without relationships cannot expose what real operating cases might lose during transfer.
Map the package before exporting
Request an index identifying each file's data type, extraction time and coverage. Row order should not serve as the link between files. Preserve source identifiers for entities and both endpoints, type and direction where needed for relationships, with the intended destination representation explained.
- Entity files: identifiers, current values and agreed fields.
- Relationships: endpoint identifiers, association type and multiple-value interpretation.
- Field dictionary: label, code, value type, list options and relevant time zone.
- History and activities: each file's coverage and unavailable information.
- Attachments: actual files where included, with record-linking references.
- Exceptions: missing, redacted or separately retrievable data and its follow-up owner.
This is a negotiation tool, not a claim that every platform exports everything automatically. The supplier identifies product, account and permission capabilities, additional work and unavailable items. The buyer prioritizes gaps before accepting the package.
Product exports have different scopes
HubSpot distinguishes record exports with current properties and associations from individual contact-data exports with available history, activities and additional options. Column and association choices affect results; CSV's all-associated-records option means a default association limit is not universal.
Its Files documentation describes a separate permission-controlled ZIP export of selected files. This does not establish that a CRM record export automatically contains every activity attachment. A text link proves neither the file's presence in the package nor continued access after departure.
Read the sample as its recipient would
Under explicit authorization in a suitable environment, ask a specialist to reconnect the sample using identifiers. In the workwear example, they identify which company owns the deal despite the contact's two associations, then link the note and file to the correct record and flag ambiguity.
For a changed field, separate its current value from historical events: change time, meaning and available source. Do not invent missing history or treat the whole file's modification time as every field's change time. Redacted values require documented reading limits rather than attempts to bypass redaction.
Include an Arabic name, list options and a date with a known time zone so successful file opening does not conceal interpretation problems. Where the destination converts codes to labels, retain the mapping and its version. Familiar labels should not replace stable record identifiers.
Accept known coverage
Record in-scope entity, relationship and file counts alongside sample results. Distinguish present and reconnectable, present but unexplained, and not delivered. Counts do not establish relationships, and samples do not establish inspection of every row; each evidence type has a different boundary.
Specify the data snapshot time, treatment of later changes and responsibility for resolving and accepting exceptions. Discuss access, retention and sharing with authorized owners. Do not send customer data to a new party merely to try a file or assume an unverified legal entitlement.
CRM implementation scope places these deliverables in the proposal, supported by ownership and handover questions. Bring the package map and sample when discussing CRM with Nextwave to define required portability.
Export scope references
Relevant record export, individual contact data and file export sections were read on 4 November 2026. Prepared with AI assistance and information and translation review, without exporting or sending data.
