delete-initial-resource

To remove built-in CRM resources safely, delete the specific component folders and follow comprehensive cleanup guides to prune cross-cutting references from schemas, config props, i18n keys, and data provider methods. This ensures no broken references remain and your build passes.

When deleting initial CRM entities, shared subsystems like notes and activity logs require adjustment to remove dependent references. The cleanup process guides you through modifying these shared subsystems to prevent type errors and broken functionality.

After stripping CRM entities, clean up backend schema migrations and FakeRest dataProvider methods by pruning the removed resource's methods and adjusting the schema. The process includes database reset checks to verify the backend functions correctly without the deleted entities.

Yes, you can customize Atomic CRM to build a contact-only application by stripping out deals and tasks. The cleanup process removes the resource folders, narrows union types, removes config props, and verifies the build passes all typecheck and lint checks.

Manually deleting CRM components causes type errors because built-in resources like contacts, companies, and deals have cross-cutting references across frontend components, backend schemas, config files, and shared subsystems that break when removed without comprehensive dependent file cleanup.

After removing CRM resources, verification requires running typecheck, lint, and database reset checks to confirm no broken references remain. These checks ensure the frontend components, backend schemas, and shared subsystems all function correctly without the deleted entities.