Why are similar fields visible on Account and Kernel Account?
Last updated: June 21, 2026
Short answer
Similar fields can exist on Account and Kernel Account because they serve different purposes. The Kernel field stores Kernel's researched value. The Account field is the operational CRM field your team may already use.
Keeping them separate makes review, override, and controlled writeback safer.
Check this first
- Which object owns the field?
- Is the Account field customer-owned or Kernel-owned?
- Is the Kernel value being copied to Account by mapping or automation?
- Does the customer need both fields for comparison during rollout?
What to send support
- Field labels and API names for both fields.
- Example Account ID.
- Whether the issue is duplicate field confusion, missing data, or writeback.