Skip to content

Feedback no bulk notion import without asking

Justin's real CreatorTrack notes are created NATIVELY in the app; the old Notion Inbox/Knowledge DBs are legacy he is abandoning, NOT a corpus to migrate wholesale. On 2026-07-03 I bulk-imported 46 Notion notes into his CreatorTrack justin workspace (id 67) knowledge inbox, which BURIED his one real feedback note among clutter. He was not happy. I reverted it (deleted the 07:18 import batch; Notion originals untouched, so nothing lost).

Why: he keeps active notes in CreatorTrack directly; Notion is being decommissioned by REPOINTING reads/writes (the [[reference_creatortrack_bot_api]] cutover), not by copying its data over. Migrating DEFINITIONS (habit defs) was wanted; migrating his note CONTENT was not.

How to apply: when a CreatorTrack surface looks empty, do NOT assume the fix is importing Notion data. Ask first. Bulk data migration from Notion is opt-in per-surface with explicit go-ahead. Additive imports still bury/clutter even when nothing is deleted. See [[notion-decommission-2026-07-02]].

Auto-memory addendum 2026-07-03T07:41:39.120660

Do not bulk-import or bulk-migrate content from Notion (or any legacy system) into CreatorTrack without asking first, even when a workspace/collection looks sparse.

Why: Justin's real content (feedback notes, ideas) lives natively in CreatorTrack. A low note count in a workspace does not mean content is "stranded in Notion" needing migration, it can just mean he hasn't written much there yet. During the Notes/Knowledge overhaul (2026-07-03), an agent saw few notes in workspace 67 and assumed migration was needed, so it copied 41 inbox quick-notes + 6 knowledge notes from Notion into CreatorTrack. This buried Justin's two actual notes (a long feedback note and a medications-habit idea) under 46 imported items, and he initially reported notes as "lost." Nothing was actually deleted (Notion untouched, import was additive), but the clutter had to be manually identified and removed to restore his real notes to visibility.

How to apply: Before importing/copying any content from Notion (or other legacy stores) into CreatorTrack, LifeOS, or any other canonical data store, explicitly ask Justin first. Read-repointing bot tools to query CreatorTrack instead of Notion is fine and encouraged (that's the actual Phase 2 decommission goal), but do not also copy the underlying content unless he confirms he wants it migrated.

[auto-memory session c13c7aac-6db6-4f78-86c1-601ee921164b, confidence 0.90]