Customer database schema

Looks good

your database looks good,

but please note, Laravel's naming convention for pivot tables (CustomerAddresses) is

singularized table names, in alphabetical order separated by an underscore.

so you can rename the pivot table (CustomerAddresses) to be (address_customer)

its the best practice.

also you can set a composite primary key for (CustomerAddresses) table

['customer_id' , 'address_id'], to prevent multiple insertion for the same customer with

the same address instead of using (id) as primary key.

can one address belong to many customers? If not then you are over complicating it and you can just have a company_id on the address table.

Even if a company did share a physical address with another, I would still duplicate it since one company could suggest an edit to the address.

So, no need for a pivot as its not a many-many relationship

It is also convention that all table names are plural and lowercase, but appreciating that your diagram might be showing models

(what software did you use for the relationship diagram)

@Snapey you're right, i think there's no need for a pivot table. So this is what i have now and i think this should be fine, isn't it? :)

So each account has an account type which can be a customer or a lead. Each account can have many addresses and each account can have many contacts. And each account belongs to an owner ( user ). A user can have of course many accounts.

I am using quickdatabasediagrams.com for the database schema designer

Yes, this looks fine.

Depending on how global the accounts will be (I see you have country table), you might want to store a timezone for a contact or account so that users can tell what time to contact them or if sending emails, sending them at a specific time for the contact.