Skip to main content

Managing Custom Objects in Kyrios Systems

Custom objects allow you to manage data, relationships, and processes that go beyond standard Kyrios objects such as Contacts, Companies, and Opportunities. They provide flexibility while still integrating fully with workflows, reporting, and automations.

Updated over 2 months ago

Who This Is For / When to Use

This article is for account admins who need to:

  • Decide whether a custom object is the right solution

  • Understand when to use standard objects instead

  • Design scalable data structures without limiting platform features


What Custom Objects Are Used For

Custom objects are best suited for:

  • Tracking entities that are not people or companies

  • Managing structured data with unique fields

  • Creating relationships between specialized records and standard objects

They extend Kyrios without replacing core objects.


When to Use Custom Objects

Use custom objects when your data or process does not fit into existing Kyrios objects.

Common Scenarios

  • Unique business processes or relationships
    Track records that do not logically belong to Contacts, Companies, or Opportunities.

  • Additional structured data
    Store detailed information such as inventory items, properties, assets, or registrations.

  • Extending platform functionality
    Associate custom objects with standard objects to enable advanced workflows and reporting.


When to Use Standard Objects Instead

In some cases, standard Kyrios objects are the better choice.

Consider These Limitations First

  • Feature availability
    Some features, such as bulk marketing emails, are available only for Contacts.

  • Data duplication risk
    Creating custom objects that mirror existing data can cause inconsistencies.

  • Unnecessary complexity
    Overusing custom objects can make reporting and automation harder to manage.

If a standard object meets your needs, avoid creating a custom object.


Practical Examples

Example: Real Estate Business (Use Custom Object)

A property management company creates a Homes custom object to track:

  • Location

  • Size

  • Availability

  • Maintenance records

Homes are associated with Contacts (buyers or tenants) and Opportunities (sales or rentals).


Example: Veterinary Clinic (Use Custom Object)

A veterinary clinic creates a Pets custom object to store:

  • Medical history

  • Vaccination records

  • Appointment data

Each pet record is associated with an owner Contact.


Example: Event Attendees (Do Not Use Custom Object)

If you need to:

  • Send invitations

  • Track RSVPs

  • Send follow-up emails

Use Contacts instead. Custom objects do not support bulk marketing emails.


Example: Law Firm Client Communications (Do Not Use Custom Object)

If Opportunities already track cases and interactions, creating a separate custom object for communications adds unnecessary complexity. Log communications within existing records instead.


Importing Data Into Custom Objects

Custom objects support CSV imports.

You can:

  • Bulk import records

  • Map CSV columns to custom fields

  • Associate imported records with existing Contacts during import

This allows large datasets to be added without manual entry.


Platform Behavior to Keep in Mind

  • Custom objects integrate with workflows, automations, and reporting

  • Associations enable cross-object visibility

  • Some platform features remain exclusive to Contacts


FAQ

What are custom objects?

Custom objects let you store and manage data that does not fit into standard Kyrios object categories, providing flexibility in how information is structured and used.

When should I use custom objects instead of standard objects?

Use custom objects when the data you need to track cannot logically live inside Contacts, Companies, or Opportunities.

Can custom objects be linked to standard objects?

Yes. Custom objects can be associated with Contacts, Companies, and Opportunities to create complex relationships and workflows.

Will using custom objects limit platform features?

Some features, such as bulk marketing emails, are available only for Contacts. Always confirm feature requirements before creating a custom object.

How do I create and manage custom objects?

Admins can create custom objects from Settings > Objects, then define fields, associations, and use them in workflows and reporting.

What should I consider before creating a custom object?

Confirm that a standard object will not work, avoid duplicating existing data, and ensure required features are supported.

Can custom objects track unique business processes or relationships?

Yes. Custom objects are designed specifically to track specialized processes and relationships, such as properties, pets, or assets.

Can I import custom object data from a CSV file?

Yes. You can bulk import CSV data and associate records with existing Contacts during the import process.

Did this answer your question?