DBCC RESULTS - 1719 Errors - how best to proceed with repair

A production database which is continually updated with external data has reported following an integrity check 1719 errors. These can be grouped into: 116 x Table error: Object ID 0, index ID -1, partition ID 0, alloc un it ID 14918418583781376 (type Unknown), page ID (1:358049) contains an incorrect page ID in its page header. The PageId in the page header = (45:3473461). Summarised: CHECKDB found 0 allocation errors and 118 consistency errors not associated with any single object. 544 x Object ID 854294103, index ID 6, partition ID 720575941117214 72, alloc unit ID 72057594157203456 (type In-row data): Page (1:358048) could not be processed. See other errors for details. Summarised: CHECKDB found 0 allocation errors and 544 consistency errors in table 'Rpm.TrainRecord' (object ID 854294103). 1021 x Table error: Object ID 1327343793, index ID 4, partition ID 72057594114670592, alloc unit ID 72057594160611328 (type In-row data), page ID (1:7031943) contains an incorrect page ID in its page header. The PageId in the page header = (1:4795983). Summarised: CHECKDB found 0 allocation errors and 1021 consistency error s in table 'Audit.AuditLog' (object ID 1327343793). 31 x Object ID 1349579846, index ID 7, partition ID 7205759410936 2176, alloc unit ID 72057594154647552 (type In-row data): Page (3:600863) could not be processed. See other erro rs for details. Summarised: CHECKDB found 0 allocation errors and 31 consistency errors in table 'Rpm.AlarmEventRecord' (object ID 1349579846). The end output is repair_allow_data_loss is the minimum repair level for the e rrors found by DBCC CHECKDB ([databasename]). We have backups, it seems the issue has come about following a move of the DB from one server to another (over last weekend). Checking the old server, there are no consistency errors at all. The database functions fine and can be backed up / restored. I'm guessing I need to repair with data loss - but can I do anything better than that?