Problem in Upgrading to Sugar 8.0

Hmm its failing pretty early.  Your upgrade log is failing at <your_instance>/upgrade/scripts/post/2_Rebuild.php which is very early in the upgrade process.  Some notes: 

MySQL error 1071: Specified key was too long; max key length is 1000 bytes

'1000 limit' is consistent with <=5.6. In 5.7 this limit has increased to 3072 which should be plenty enough to index a utf-8 varchar(255). The fact that you are getting it on 5.7 means you likely have some non-default setting in your mysql instance or perhaps dont actually have 5.7 installed?  You could always try reinstalling MySQL or removing any weird settings you have in my.cnf to see if this goes away.  

Configuration variable date.timezone is not set, guessed timezone UTC. Please set date.timezone="UTC" in php.ini!

This is a really important one and should have been set when you first installed Sugar.  Find your php.ini (for example on Debian/RHEL its at etc/php.ini)  and add the line for your time zone.  my setting is:

[Date]

    date.timezone = "America/New_York"

You can find a list of supported plain text time zones here: PHP: List of Supported Timezones - Manual 

Unknown column 'outbound_email.email_address_id' in 'field list'

here is my output for the outbound_email table.  It doesnt exist in my 8.0 instance either but I'm not sure thats stopping you.  

 mysql> describe outbound_email;
+-------------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------------+--------------+------+-----+---------+-------+
| id | char(36) | NO | PRI | NULL | |
| name | varchar(50) | YES | | NULL | |
| type | varchar(15) | YES | | user | |
| user_id | char(36) | NO | | NULL | |
| mail_sendtype | varchar(8) | YES | | smtp | |
| mail_smtptype | varchar(20) | YES | | other | |
| mail_smtpserver | varchar(100) | YES | | NULL | |
| mail_smtpport | int(5) | YES | | 0 | |
| mail_smtpuser | varchar(100) | YES | | NULL | |
| mail_smtppass | varchar(100) | YES | | NULL | |
| mail_smtpauth_req | tinyint(1) | YES | | 0 | |
| mail_smtpssl | int(1) | YES | | 0 | |
+-------------------+--------------+------+-----+---------+-------+
12 rows in set (0.00 sec)
 

If you wanted to, you could add the field just to make the error go away.  In MySQL or PHPmyAdmin perform the following:

Table 'crm.audit_events' doesn't exist

My instance doesnt have this table either.  I dont this this is stopping you either.

That is curious.

The index idx_del_category_name_acltype_aclaccess was created without issue in my instance.

I do have outbound_email.email_address_id

  `email_address_id` char(36) DEFAULT NULL,

and I also have the audit_events table:

CREATE TABLE `audit_events` (
`id` char(36) NOT NULL,
`type` char(10) DEFAULT NULL,
`parent_id` char(36) NOT NULL,
`module_name` varchar(100) DEFAULT NULL,
`source` text,
`data` text,
`date_created` datetime DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `idx_aud_eve_ptd` (`parent_id`,`type`,`date_created`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

I suspect these should have been created for you.

I had some problems with the v8.0.0 upgrade and went straight for v8.0.1

You may want to try that approach.

FrancescaS

I had the same issue. In addition to the above tables, my instance was also missing the erased_fields table;

CREATE TABLE `erased_fields` (
 `bean_id` char(36) NOT NULL,
 `table_name` varchar(128) NOT NULL,
 `data` text,
 PRIMARY KEY (`bean_id`,`table_name`)
 ) 

MySQL error 1071: Specified key was too long; max key length is 1000 bytes
It occured to me that the error can still happen with a 5.7+ mysql if your database keeps some of its tables in the MYISAM engine. 

To fix this, you would have to play this query to collect all the query you will need to play ( tables that are still in MyISAM on your schema ) : 

SELECT CONCAT('ALTER TABLE ', TABLE_SCHEMA, '.', TABLE_NAME,' ENGINE=InnoDB;') FROM Information_schema.TABLES WHERE TABLE_SCHEMA = '<your_db_name>' AND ENGINE = 'MyISAM';

and then execute the queries this query will construct.

Hope it helps !