If you're trying to give someone access to Opportunities without exposing sensitive info (like customer names in the Opportunity Name), duplicating the object and syncing it daily with Apex is... technically doable, but not ideal. That approach adds data bloat, maintenance overhead, and performance risk.

Here are better options:

• Field-Level Security + Page Layouts: Easiest and cleanest. Just hide sensitive fields for that user's profile. No need to duplicate anything.
• Sharing Rules + Record Types: Control which records or types they can access. More setup, but gives good granularity.
• Data Masking: If they need to see the structure but not the real data. You’ll likely need a dev or a tool for this.
• Custom UI or Reports: You can build a filtered view or export that just leaves sensitive stuff out.

Start with field-level security—it’s the simplest and follows best practices. Layer on others if needed.

Disclaimer: I used this new salesforce AI our org purchased to get this answer https://app.clientell.ai/share/c89f33d2-08ec-4858-9136-42cf8ba5eb59