Replacing composite key with surrogate

I have the following table that has a couple of million rows in it and is 99% fragmented virtually all of the time. My plan was to insert a IDENTITY field as a surrogate key to replace the current composite 6 field primary, then make the current key a unique key for referential integrity and recreate the indexes.

    CREATE TABLE [dbo].[Autocompleter](        [CountryId] [int] NOT NULL,        [ProvinceId] [int] NOT NULL,        [LocationId] [int] NOT NULL,        [PlaceId] [int] NOT NULL,        [EstabId] [int] NOT NULL,        [LocaleId] [int] NOT NULL,        [Title] [varchar](400) NOT NULL,        [Hotels] [int] NULL,        [AlternateTitles] [varchar](4000) NULL,        [EnableHotels] [bit] NOT NULL,        [EnableHolidays] [bit] NOT NULL,        [DisplayPriority] [int] NOT NULL,     CONSTRAINT [PK_autocompleter_1] PRIMARY KEY CLUSTERED     (        [CountryId] ASC,        [ProvinceId] ASC,        [LocationId] ASC,        [PlaceId] ASC,        [EstabId] ASC,        [LocaleId] ASC    )

Any gotchas I should be looking out for ? if it is an identity field I am thinking this should not break code that inserts into the table (as long as it specifies the columns explicitly)

I plan to create a new clustered index on the surrogate key and then make the current clustered index on the 6 fields a NC index.