Back to all articlesCRM migration

Keep Historical CRM Notes Understandable After Import

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A customer note can survive a CRM import word for word and still become misleading. If its visible author becomes the migration administrator and its date becomes import day, a reader may mistake an old commitment for a recent one. If several notes receive the same timestamp, their apparent sequence can reverse the meaning of the conversation.

For CRM migration historical notes, preserve two distinct layers: the original note and its legacy context, then the metadata describing its import. Keep the source body intact, label authorship and time explicitly, retain a stable link to the intended record, and test what readers actually see—not just whether rows were accepted.

The format and fictional worked example below provide a practical starting point. They are recommended operating practices, not claims about controls available in a particular CRM.

1. Decide what a faithful historical note must preserve

Define the acceptance contract before mapping fields. A successful import should let a reader answer: who wrote this, when was it recorded, what record did it belong to, and what happened before or after it?

Separate essential evidence from convenient presentation. A native author field is convenient, but a clearly labelled legacy author in the note can preserve attribution when that field cannot be set. A native historical creation date is useful, but it does not replace checking how the activity feed sorts notes.

  • Body: preserve wording, meaningful line breaks, and distinctions between separate entries.
  • Authorship: retain the source author identifier and available display name without assuming that person has an active destination account.
  • Time: retain the original value, its precision, and any known timezone or offset. Distinguish creation from later edits.
  • Relationship: preserve the source record reference and map it to the intended destination record.
  • Identity: keep a stable source note identifier so retries and investigations can refer to the same item.
  • Context: preserve relevant parent-note relationships and attachment references, identifying anything not migrated.

Do not turn a migration into a rewriting exercise. Correcting spelling, expanding abbreviations, or replacing several notes with a summary changes the evidence readers receive. If a source passage is unclear, preserve it and label the uncertainty separately rather than silently improving it.

2. Define a format that separates legacy facts from import facts

Use native destination fields where they can faithfully represent source values. Where they cannot, use a consistent labelled block in the note or another accessible representation. Confirm availability and behaviour in the destination workspace and current plan before choosing the implementation.

A portable format has three parts: legacy context, original body, and import provenance. Keep the body boundaries explicit so a reader can distinguish a salesperson's words from migration annotations.

Historical note — migrated record

LEGACY CONTEXT
Source system:
Source note ID:
Original author name:
Original author ID:
Originally recorded:
Original time basis:
Last edited in source:
Source record:
Destination record:
Related note or attachment references:

ORIGINAL NOTE BODY
[Preserved source text]
END ORIGINAL NOTE BODY

IMPORT PROVENANCE
Imported at:
Imported by:
Import batch:
Conversion notes:

Not every note needs a long visible header. If structured fields are reliably displayed and searchable, some of this information can live there. The trade-off is readability versus portability: a compact display is easier to scan, while embedded labels are less dependent on a particular screen layout. Check exports as well as the main record view before deciding.

Reserve labels such as Original author for source facts and Imported by for the operator or service performing the migration. If the destination's native creator remains the importer, make that distinction visible near the note. Do not create an apparent user attribution merely because two people share a name.

3. Handle timestamps without inventing certainty

A timestamp is not necessarily a complete point in time. A source might contain an explicit offset, a local clock time without a timezone, or only a calendar date. Preserve what is known rather than filling missing parts with plausible values.

  • Explicit offset: retain the source timestamp and, if needed, add a normalized value for sorting. Identify the normalized value as derived.
  • Local time with a documented source timezone: retain the local value and the timezone basis used for conversion. Review ambiguous clock-change cases rather than silently choosing an offset.
  • Unknown timezone: label it unknown. Do not present a UTC conversion as established fact.
  • Date only: preserve date-only precision. If an import mechanism requires a time, document any technical placeholder and do not display it as the original event time.

Also distinguish when someone recorded a note from when the described event occurred. A note entered later about an earlier call is still a later-created note. Do not extract a date from its prose and substitute it for its creation timestamp.

Agree on an ordering rule before importing. Use original creation time where comparable. For equal timestamps, use a source sequence if one exists. Otherwise, a stable source ID can provide a repeatable display order, but it does not prove which event came first. Date-only or uncertain-time notes should not be presented as having a precise sequence they never had.

4. Use this filled fictional conversion example

Fictional worked example: All names, identifiers, text, dates, and batch details in this example are hypothetical. A migration team is moving notes for a fictional account, Alder Workshop. The destination records the importing service as the native creator and cannot preserve the source creation date in that field. The team therefore uses a labelled historical-note body and retains a separate mapping manifest.

Source entry

Source system: Legacy CRM
Source note ID: N-0472
Author name: Maya Chen
Author ID: U-018
Created: 2024-02-13T16:40:00+00:00
Last edited: Not supplied in export
Linked source record: Account A-0087 — Alder Workshop
Related source note: N-0469
Attachment reference: None

Source text:
Spoke with Elena about the revised installation date.
Do not confirm Friday yet; she is checking site access.
Call back after her facilities meeting.

The record crosswalk maps source account A-0087 to destination account AC-0214. Related note N-0469 is mapped separately. The destination representation does not claim that Maya created the imported destination object.

Destination representation

Historical note — migrated record

LEGACY CONTEXT
Source system: Legacy CRM
Source note ID: N-0472
Original author name: Maya Chen
Original author ID: U-018
Originally recorded: 2024-02-13T16:40:00+00:00
Original time basis: Explicit UTC offset in source export
Last edited in source: Not supplied in export
Source record: Account A-0087 — Alder Workshop
Destination record: Account AC-0214 — Alder Workshop
Related note: Source N-0469; destination DN-0908
Attachment references: None listed in source export

ORIGINAL NOTE BODY
Spoke with Elena about the revised installation date.
Do not confirm Friday yet; she is checking site access.
Call back after her facilities meeting.
END ORIGINAL NOTE BODY

IMPORT PROVENANCE
Imported at: 2025-05-06T09:15:00+00:00
Imported by: Migration service
Import batch: HIST-2025-05-06-A
Conversion notes: Native destination creator and creation date
represent import activity, not original authorship or note time.

Filled review checks

  • Body fidelity — pass: the three source lines match the original-body section; no summary or wording changes were introduced.
  • Attribution — pass: Maya's name and source user ID are visible; the importing service is separately labelled.
  • Time — pass: the original timestamp retains its explicit offset, while import time appears only as import provenance.
  • Record link — pass: opening the note's parent record leads to destination account AC-0214, matching the approved crosswalk.
  • Related context — pass: destination DN-0908 corresponds to source note N-0469 and is available to the reviewer.
  • Chronology — fail pending remedy: the ordinary activity feed places the note under import day. The labelled timestamp is accurate, but the default timeline does not provide historical ordering.

This result is not a full acceptance. The team must provide an approved historical view ordered by original time, another usable chronological representation, or a clearly documented limitation accepted by the record owner. Accurate text alone does not fix a misleading timeline.

5. Validate relationships and retry safety before scaling

Map notes using stable identifiers, not company names or contact email addresses alone. Names can repeat, and a source record may have been merged, split, or excluded. Keep a crosswalk recording the source record, destination record, mapping status, and reviewer decision for exceptions.

Quarantine unresolved notes rather than placing them on a convenient-looking record. If a note originally belonged to a contact, moving it to an account may broaden its context or audience. Treat that as an explicit mapping decision, not a harmless fallback.

Use the source system and source note ID together as the migration identity. Record the resulting destination note ID after a confirmed write. On retry, reconcile that identity against existing results before creating another note. Identical text is not a reliable duplicate key: two legitimate entries may contain the same words.

Attachments and related notes need their own checks. Preserving a filename or source link does not establish that the underlying content remains accessible. Mark missing material explicitly and retain it as an exception until its treatment is agreed.

6. Test the reading experience, not just the import report

Run automated comparisons across the batch where feasible, then inspect representative records in the interface people will use. An accepted-row count cannot show whether formatting disappeared, author labels are hidden, or a note is attached to the wrong account.

Build the pilot sample around difficult cases: inactive authors, repeated names, multiline text, equal timestamps, date-only values, edited notes, merged records, missing attachments, and retry attempts. Include a record with several related notes so reviewers can evaluate sequence.

  1. Reconcile inventory: every source note in scope has one recorded disposition—imported, intentionally excluded, or held for review. Compare totals and identifiers, not totals alone.
  2. Compare content: detect missing or truncated bodies. Permit only documented technical transformations, such as a necessary line-ending conversion.
  3. Inspect attribution and time: confirm that displayed labels do not turn import metadata into apparent historical facts.
  4. Open linked records: verify actual associations against the crosswalk, including records affected by merges.
  5. Read a sequence: ask a reviewer to identify what was recorded before and after a selected note using the available view.
  6. Check access: test with appropriate ordinary-user roles, not only the migration administrator. Historical notes should not become more widely visible merely because their representation changed.

Record both field-level and reader-level results. A note can pass exact-text comparison but fail because its context is hidden. Conversely, an attractive timeline can conceal altered wording. Both are release concerns.

7. Set failure rules and recover without compounding errors

Define blocking failures before the pilot. Wrong parent records, altered bodies, falsely attributed authorship, and unexplained missing notes should block the affected batch. Missing source facts should remain visible unknowns, not become import failures that an operator resolves by guessing.

Classify exceptions by cause: source data missing, destination limitation, mapping unresolved, or conversion defect. This makes the next action clear. A missing source timezone needs acknowledgement or evidence; a conversion defect needs corrected logic and a rerun.

Retain an unchanged source export and the conversion manifest under appropriate access controls for the agreed migration review period. Before retrying, identify which destination notes were actually created. Where authorised and supported, correct or remove only the affected imported objects using the batch and identity mapping. Do not bulk-delete by import date alone: unrelated work may share that date.

If users have already edited imported notes, avoid overwriting those changes automatically. Separate the original import defect from subsequent work and have an owner approve the repair. Re-run the same acceptance checks after remediation; a successful retry is not evidence that the original problem disappeared.

8. Make the next batch earn acceptance

Start with a pilot containing each known exception type and at least one multi-note history. Before running it, write down the chosen format, timestamp rules, ordering rule, identity key, and blocking failures.

Publish a short acceptance record with the source count, imported count, exclusions, unresolved exceptions, content mismatches, mapping failures, and chronology-review results. State the denominator for each check so a small reviewed sample is not mistaken for full-batch verification.

For the next migration session, the concrete deliverable is a reviewed version of the filled example above using your own source fields, plus a pilot manifest showing every note's disposition. Release the batch only when the agreed checks pass and any remaining limitations have a named owner and an explicit decision.

CRM migrationData qualityHistorical notesMigration testing

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