Test Sales Tool Export Requirements Before Buying

Define what must remain usable after the export

An export button can produce a perfectly readable file that still fails a buyer's portability requirement. Names without stable identifiers cannot reliably reconnect related records. Notes without their source links lose their evidential value. A contact restriction buried in an omitted activity field may disappear from the next operator's view.

Start with the business purpose: “We need to move our approved research records into another permitted system without losing relationships, provenance or operational restrictions.” Then specify the information necessary for that purpose. Do not demand every field merely because it exists, and do not assume that exporting data authorizes a new use of it.

Official documentation may distinguish export routes by object. For example, HubSpot's record-export guidance covers properties and associations while directing users to separate methods for activities such as notes. A buyer should inspect the relevant route, not infer note portability from a successful company export.

Portability test specification P-08

This completed specification uses invented records in a disposable evaluation workspace. The observations below are illustrative, not firsthand product results. Its destination is an ordinary offline review folder, not another live prospecting system.

• Scope and owner: Evaluation owner Mira checks export E-08. Include accounts A10 and A11, contacts C10, C11 and C12, and approved notes N10 and N11. Exclude unrelated workspace records.

• Account fixture: A10 and A11 both display “North Field.” Their identifiers must remain distinct. C10 and C11 belong to A10; C12 belongs to A11. Display names alone are not an acceptable joining key.

• Note fixture: N10 belongs to A10 and contains the text “Route review, phase two” plus the synthetic source URL https://example.invalid/research/a10. N11 belongs to A11 and contains an accented place name, a quotation mark and a line break. Text and associations must survive without silent alteration.

• Restriction fixture: C11 has “Do not include in campaign preparation” as an operational restriction, with the fictional reason “evaluation exclusion.” Preserve its meaning and record link. This test field is not a claim about legal consent or permission to contact anyone.

• Requested package: Record files, relationship mapping, field definitions, export timestamp and any separate note file. Identify omitted fields explicitly. Screenshots may explain settings but cannot replace the reusable records.

• Acceptance: An independent reviewer can reconstruct both account groups, attach each note, find C11's restriction and read the special characters without consulting the original interface. No guessed links are allowed.

Read the package as if access had already ended

Close the source application before checking the files. Open them with a suitable reader and inspect actual values, not merely file names. Count records by object, check unique identifiers, and trace one contact and one note back to each account. If a spreadsheet automatically reformats an identifier, distinguish that reader behavior from a source-export defect by inspecting the raw file safely.

In the illustrative result, the account and contact files preserve all identifiers. N10 and N11 arrive in a separate activity file, but that file omits account IDs. C11's restriction exports correctly. The package therefore fails the relationship criterion even though every note's text is present. Mira records “note association missing” rather than “export unavailable.” That narrower finding directs the next question.

The supplier proposes matching notes by account name. This is the deliberate counterexample: both accounts share a name, so the workaround can attach the wrong evidence. Stop reconciliation rather than inventing a mapping. Request a supported relationship export or an explicitly maintained mapping file, then rerun the independent reconstruction.

Ask what happens at the exit

Check who may initiate the export, whether the necessary format is available on the proposed plan, and whether account closure changes access. Request written answers for unresolved limits. A trial administrator's success does not establish an ordinary user's permissions or the customer's post-cancellation access.

Keep the specification, export settings and result with the purchasing record. The minimum lead-record field guide helps decide what information has a genuine operational purpose. Portability adds a separate obligation: preserving enough structure for that information to remain intelligible outside the original tool.