That db design and naming convention would drive me nuts.
Personally, I'd recreate the database using sane table/field names and follow laravel conventions (like 'id' instead of idCogHospedeiros for the pk name, etc).
I'd create migrations to recreate the sanely named tables/fields, using the plural of the word it represents (users vs user) and create the models using the singular form (User vs Users).
I'd create a seeder that would take the old data, and insert it into the new db.
I know that's not a small/trivial thing to do, but once done it will make the app a lot easier to code and fit within laravel without a lot of additional modifications (like having to override the table name in the model, or the primaryKey, or having to manually enter id's in relationship definitions, etc).
I've inherited monstrosities like that in the past and tried to make do, only to waste lots of time (and frustration) making things work with the original crap structure. Once I converted it all to laravel conventions, it was a breeze to convert the rest.
