Handle Historical Notes and Attachments That Cannot Be Imported Cleanly
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A historical note can import successfully and still become unusable: its table loses its columns, its attachment link opens the wrong file, or its final paragraph disappears. A rejected document is easier to notice than a record that looks complete but is not.
For CRM migration exceptions, choose a disposition for each affected item: convert it, migrate a clearly labeled portion, preserve it in a separately accessible archive, or hold it for exception review. Keep the original available where possible, connect the destination record to the exception, and verify retrieval using the permissions of an intended reader. Do not treat an accepted import row as proof that its history survived.
The working tool is an exception register that records what failed, what users can access instead, and what evidence supports closure. The fictional worked example below shows how to fill it for rich-text notes, oversized documents, broken links, and missing files.
1. Identify what failed before choosing a workaround
Separate the problem into content, relationships, and access. A file may be intact but attached to the wrong account. A note may retain all its words but lose formatting that distinguishes a customer request from an internal response. An archive may contain everything while remaining inaccessible to the people handling the account.
For each exception, capture:
- Source identity: the record identifier, note or attachment identifier, and original filename or title.
- Expected context: parent record, author, timestamp, and relationships that explain the material.
- Failure observed: rejection, truncation, unreadable rendering, missing content, incorrect association, or denied access.
- Evidence: export results, error details, source availability, and a description of the mismatch.
- Business consequence: what a reader might misunderstand or be unable to do.
Check the actual destination constraints in the workspace and current plan rather than assuming a file extension or size will be accepted. Test representative content, not just empty sample files. A format may be accepted while embedded images, comments, tables, or links do not survive.
Keep rejection separate from temporary transfer failure. An interrupted upload does not establish that the file is unsupported; a retry does not establish that its contents are usable.
2. Choose a disposition based on what readers need
Convert when meaning can survive the change
Conversion is appropriate when a destination-readable representation preserves the information people need. A rich-text note might become plain text with explicit speaker labels, or a complex document might gain a readable viewing copy. Preserve the source separately until the converted version has been reviewed.
The trade-off is fidelity. A visually tidy conversion can erase comments, hide annotations, or turn a meaningful table into an ambiguous sequence of values. If that changes interpretation, conversion alone is not enough.
Use partial migration only with a visible boundary
A shortened note or document summary can support day-to-day work when the full material remains accessible elsewhere. Label it as partial, explain what is excluded, and provide a retrieval route. Do not present a summary as the original historical note or attribute newly written wording to its original author.
Use a separate archive when native import is unsuitable
An archive can preserve originals without forcing them into an incompatible field. It needs a stable index, a reliable association with the CRM record, appropriate access restrictions, and a retrieval method tested by an intended user. A folder held only by the migration operator is not a dependable fallback.
Keep uncertainty in exception review
Use review when the source is missing, the correct parent record is uncertain, or conversion changes meaning. Review is a controlled unresolved state, not permission to omit the item. Give it an owner, a next action, and an explicit decision about whether affected records can proceed.
3. Fill the exception register with decisions and evidence
Fictional worked example: All identifiers, quantities, filenames, people, dates, and results in this register are hypothetical. The destination constraints are assumed for the example, not claims about any product. The archive references describe a proposed operating arrangement, not an existing product capability.
EX-01: Rich-text note loses its table structure
- Source and parent: note N-184 on account AC-042, titled “Service handover.”
- Observed exception: the trial import retained the text but collapsed a table pairing open issues with their owners. Embedded screenshots were absent.
- Disposition: convert the table into labeled issue-and-owner entries; preserve the source export and screenshots in archive package ARC-042-N184.
- Destination label: “Converted historical note. Layout changed; embedded screenshots are available in archive package ARC-042-N184. See exception EX-01.”
- Fallback access: retrieve the package through the archive index using AC-042 or N-184. If the CRM reference fails, the service operations owner can locate it from either identifier.
- Owner and state: migration analyst; closed as converted with archived original.
- Verification evidence: reviewer compared every issue-owner pair with the source, checked authorship and timestamp, opened the screenshots, and retrieved the package using a service-user account. Results recorded in evidence record EV-01.
EX-02: Document exceeds the tested upload limit
- Source and parent: attachment ATT-550 on opportunity OP-088, “Equipment survey.pdf,” hypothetically 78 MB against an assumed 25 MB destination limit.
- Observed exception: upload rejected because of size; the original opens from the source export.
- Disposition: archive the complete original as ARC-088-ATT550. Add a separately identified navigation summary to the destination rather than compressing diagrams until they become unreadable.
- Destination label: “Partial migration: navigation summary only, prepared during migration. Complete survey and diagrams remain in archive package ARC-088-ATT550. See exception EX-02.”
- Fallback access: use the controlled archive index; request assistance from the account operations owner if access fails. No public sharing link is used.
- Owner and state: account operations owner; closed as partial migration with accessible original.
- Verification evidence: source and archived file checksums matched; reviewer opened the archived document, checked diagram legibility, tested retrieval as an intended reader, and confirmed the summary points to the correct survey. Evidence record EV-02.
EX-03: Historical note contains a broken link
- Source and parent: note N-309 on account AC-063, referring to “Approved scope.”
- Observed exception: the embedded link returns a not-found response. An export package contains a similarly titled document, but the link alone does not prove it is the same version.
- Disposition: migrate the note with an unresolved-link warning. Keep the candidate document separate pending the account owner's confirmation.
- Destination label: “Historical link unavailable. A possible replacement is under review; do not treat it as the approved scope. See exception EX-03.”
- Fallback access: request the candidate through the review owner, who can also search the source export index. Do not silently redirect the old link.
- Owner and state: account owner; open, awaiting version confirmation.
- Verification evidence: failed-link check recorded; candidate filename and source location recorded; no equivalence approval recorded. Evidence record EV-03 explicitly remains incomplete.
EX-04: Attachment metadata exists, but the file is missing
- Source and parent: attachment ATT-771 on case CS-120, “Site photographs.zip.”
- Observed exception: metadata appears in the export manifest, but no corresponding file was found in the export package or the source retrieval attempt.
- Disposition: preserve available metadata as a missing-file entry; do not fabricate an empty attachment to satisfy a count.
- Destination label: “Historical attachment unavailable at migration. Filename and association preserved; file contents not recovered. See exception EX-04.”
- Fallback access: no content fallback currently exists. Service operations will request another source export and ask the case owner whether an identifiable copy exists.
- Owner and state: service operations lead; unresolved. Case history may proceed with the warning, but the attachment is not counted as migrated.
- Verification evidence: manifest entry, package search results, and unsuccessful source retrieval recorded in EV-04. Recovery has not been demonstrated.
4. Put the limitation where the reader will encounter it
The register helps the migration team, but destination users need the warning alongside the affected history. Where the destination permits it, place a concise label on the note, attachment reference, or related record. Otherwise, use a clearly named companion entry connected to that record.
A useful label states the condition, its consequence, and the next route. “Partial migration: images excluded; original available through archive reference…” is more useful than “Migration issue.” For missing content, say it is unavailable rather than implying an archive exists.
Preserve original authorship separately from migration annotations. Record who created the summary or conversion and when. This prevents a new explanation from appearing to be a historical customer statement.
Avoid putting sensitive excerpts into a broadly visible warning. The label should help readers find the material without exposing content to people who could not access the original.
5. Verify fallback access, not just archive existence
A checksum match supports byte-for-byte preservation; it does not prove readability, correct record association, or appropriate access. A successful administrator download proves even less about the experience of an ordinary user.
For archived exceptions, verify the full path: locate the CRM record, read its warning, resolve the archive reference, open the intended material, and confirm that its identity matches the register. Test with a representative authorised user and check that an unauthorised user cannot retrieve restricted material.
OWASP's authorization guidance recommends least privilege, deny-by-default access, and permission checks on every request. Apply those principles to the archive as well as the CRM; knowing a file identifier should not become a substitute for permission.
Also test the fallback when a direct link fails. A stable archive reference and named retrieval owner provide a recovery route when a folder moves or a link changes. Record the test identity, result, and evidence location without storing credentials in the register.
6. Recover failures without creating duplicate history
Keep source identifiers attached to every remediation attempt. When a conversion fails review, revise the derivative and update the same exception rather than importing another unexplained copy. Mark superseded destination entries clearly so users know which version to use.
If an archived file later proves unreadable, reopen the exception. Try recovery from the preserved source, then repeat both content and access checks. Do not leave the register closed merely because an earlier transfer succeeded.
When a missing file is recovered, verify its parent relationship and version before replacing the unavailable-file warning. Retain the recovery history in the register. A similar filename is not sufficient evidence that the original has been found.
For unresolved items that could materially change a handover or customer response, require the responsible business owner to decide whether the affected work can proceed. A migration operator should not silently make that judgment through omission.
7. Reconcile outcomes before signing off
Count each source item under one primary disposition so archived originals and converted copies do not inflate the totals. Track verification separately from disposition: an item can be assigned to an archive while access remains unverified.
- Converted: derivative checked for meaning and association.
- Partial: limitation labeled and full-content route tested where available.
- Archive-only: reference present and intended-user retrieval tested.
- Unresolved: owner, evidence gap, next action, and impact decision recorded.
For the hypothetical register above, all four exceptions have destination warnings and named owners. Two have verified fallback access; the broken-link and missing-file cases remain unresolved. Reporting all four as successfully migrated would conceal the remaining work.
Next action: run a small trial batch that includes each exception type, then reconcile every source item to a disposition. Before expanding the batch, require every exception to have an owner and an honest destination label. Report verified retrievals and unresolved gaps separately. That gives the team a measurable basis for proceeding without confusing visible records with complete history.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications