Hello Ian,

Currently we give the user the option of exporting visualizations and then, on import, the user can create a new index pattern or choose an existing pattern with which to associate those visualizations. If we assume association based on the index pattern rather than the id, we run the risk of attempting to associate a visualization with an entirely different index that just happens to be found/identified with the same pattern. The user is of welcome to make that mistake, we just don't want to automate it!