Upgrading a Mac from macOS Ventura to macOS Sequoia can be as simple as installing the new operating system over the old one. But when the same user account has been carried forward for many years, a clean installation becomes much more attractive.
The difficult part is not reinstalling macOS. It is deciding what should be brought to the new installation and what should be left behind.
Documents, music files and ordinary folders are easy to copy. Mail databases, Messages, Photos libraries, application settings, browser profiles, local databases and the enormous contents of ~/Library are much less obvious.
This guide explains a practical way to move from macOS Ventura to macOS Sequoia on a 2018 Mac mini while keeping important personal data without automatically importing years of obsolete settings, caches and application leftovers.
Should You Clean Install macOS Sequoia Instead of Upgrading Ventura?
For a relatively new macOS installation, an in-place upgrade is usually the easiest option. A Mac installation that has accumulated applications, preferences and user data through many generations of macOS is different.
A long-lived account can contain:
- preferences belonging to applications that no longer exist,
- old launch agents and login items,
- application databases from previous versions,
- unused browser extensions,
- abandoned support files,
- obsolete caches,
- old printer and scanner components,
- network extensions and VPN components,
- audio drivers and plug-ins,
- licensing services,
- old synchronization utilities,
- software update helpers,
- large iPhone and iPad backups.
That does not mean that a large ~/Library folder is necessarily bad. A Mac that has been used for many years will naturally have a large Library. The problem is that it becomes difficult to distinguish valuable application data from files that are no longer necessary.
When moving from an older external SATA SSD to a faster Thunderbolt-connected SSD, this is therefore an excellent opportunity to start with a genuinely fresh copy of macOS Sequoia.
The most useful approach is not a completely manual migration and not a complete Migration Assistant migration. It is a selective migration.
The Safest Strategy: Clean macOS, Fresh Apps, Selective Personal Data
For a Mac with a user account that has existed for many years, a good migration strategy is:
- Keep the existing Ventura startup disk unchanged.
- Create a separate backup before doing anything else.
- Install macOS Sequoia cleanly on the new SSD.
- Create a fresh user account.
- Sign in to the Apple Account and allow cloud-based data to synchronize.
- Reinstall applications from current installers.
- Move ordinary personal files manually.
- Migrate application-specific data only when it is actually needed.
- Keep the old Ventura disk available as a read-only historical reference for several weeks or months.
This produces something close to a new Mac while preserving access to the old environment.
The important principle is simple:
Move data, not history.
A 15-year-old preference file has little value if the corresponding application was removed ten years ago. A 15-year archive of email, photographs or documents may be extremely valuable.
The two should not be treated equally.
What Does Migration Assistant Transfer?
Apple’s Migration Assistant can transfer information from another Mac, a Time Machine backup or another startup disk. Apple separates migration into several major categories, including:
- Applications
- User accounts
- Other Files & Folders
- Privacy & Security Settings
- System & Network settings
Within a user account, Migration Assistant can also expose additional choices for categories such as documents, pictures, movies, Desktop and Downloads.
This distinction is important because Applications and User Accounts are separate migration categories.
Selecting an application is therefore not the same thing as selecting the application’s user data.
Apple does not document Migration Assistant as a system where every folder inside ~/Library/Application Support is individually matched against the applications selected in the Applications category.
In other words, it is unsafe to assume:
“If I do not migrate Application X, Migration Assistant will automatically exclude every preference, database and support file belonging to Application X.”
That is not a level of granular control that Apple’s public Migration Assistant interface provides.
Apple’s current description of the migration categories can be found in its Migration Assistant documentation.
Where Does ~/Library Go in Migration Assistant?
The hidden Library inside a home folder is fundamentally user data. It contains much of the state that makes one macOS account different from another.
Typical locations include:
~/Library/Application Support~/Library/Preferences~/Library/Containers~/Library/Group Containers~/Library/Mail~/Library/Messages~/Library/Safari~/Library/Calendars~/Library/Accounts~/Library/Keychains~/Library/Mobile Documents~/Library/MobileSync
A full migration of an existing user account is therefore very different from simply dragging Documents, Desktop and Downloads to the new installation.
This is also the main reason that migrating an entire old account can partially defeat the purpose of performing a clean installation.
The operating system itself is fresh, but much of the old user’s software state can return with the migrated account.
Does Application Support Only Move When an Application Is Selected?
Do not design a migration around that assumption.
Application binaries in /Applications and user-specific application data in ~/Library are conceptually different things. Migration Assistant presents applications and user accounts separately, and Apple does not promise a one-to-one filtering mechanism between the two.
For maximum cleanliness, reinstall applications manually and migrate only the application data that proves necessary.
How to Transfer Apple Mail from Ventura to Sequoia
Mail should be handled according to where the messages are actually stored.
IMAP, Exchange and iCloud Mail
If an account uses IMAP, Microsoft Exchange or iCloud Mail and the complete mailbox exists on the server, there is usually little reason to copy the old local Mail database.
Add the account to the clean Sequoia installation and allow Mail to synchronize again.
This is generally preferable because Sequoia builds its own current Mail database and indexes rather than inheriting years of local database history.
POP Accounts and “On My Mac” Mailboxes
This is different.
Messages stored only locally may not exist on the mail server. Those messages must be protected before the old installation is retired.
Apple Mail can export mailboxes in the standard .mbox format. On the old Mac:
- Open Mail.
- Select the important local mailbox.
- Choose Mailbox > Export Mailbox.
- Save the exported mailbox to a safe location.
On the clean installation:
- Open Mail.
- Choose File > Import Mailboxes.
- Select the Apple Mail or mbox option.
- Import the archive.
This is substantially cleaner than blindly replacing the entire Mail directory in the new user’s Library.
Why Copying ~/Library/Mail Is Not the First Choice
The Mail folder contains much more than readable messages. It can include databases, indexes, metadata, attachment structures and version-specific internal organization.
Copying an entire Mail directory from one macOS generation into another can work in some circumstances, but it should be considered a recovery technique rather than the preferred migration method.
If mail exists on a server, synchronize it. If mail exists only locally, export it.
How to Transfer Messages and iMessage History
Messages is another application where the visible conversations are backed by a database rather than a convenient collection of individually readable text files.
The cleanest solution is Messages in iCloud.
Before abandoning the Ventura installation, open Messages and verify that Messages in iCloud is enabled and fully synchronized.
On macOS this can be checked in:
Messages > Settings > iMessage > Enable Messages in iCloud
After signing into the same Apple Account on the Sequoia installation and enabling Messages in iCloud, the conversation history stored in iCloud becomes available to the new installation.
Apple specifically states that Messages in iCloud keeps message history synchronized between supported Apple devices.
This is considerably safer than manually replacing database files inside the Library.
What if Messages in iCloud Was Never Enabled?
Then the old installation becomes much more important.
Do not immediately delete, modify or repurpose the Ventura disk.
A complete Migration Assistant transfer of the user account may be appropriate if preserving local Messages history is more important than achieving an absolutely pristine user Library.
Another strategy is to enable Messages in iCloud on Ventura first, allow synchronization to finish, verify the history on another Apple device where possible, and only then configure Messages on Sequoia.
Manually dropping an older Messages database into a newly active Sequoia account is not a good first-line migration strategy.
How to Transfer an Apple Photos Library
Photos should also be treated as a database library rather than as a normal directory containing image files.
If iCloud Photos Is Enabled
Sign into the same Apple Account and enable Photos synchronization on the new system.
Apple’s iCloud Photos service keeps the photo library synchronized between devices. Depending on the library size and connection speed, rebuilding the local library can take considerable time.
If storage is available and a complete local copy is desirable, select Download Originals to this Mac after synchronization is configured.
If the Photos Library Is Local
The library is normally stored in the Pictures folder as a Photos Library package.
Copy the entire library package. Do not open it and manually copy its internal directories.
After copying the library to its destination:
- Quit Photos.
- Hold the Option key while opening Photos.
- Select the copied library.
- Open it.
- If required, designate it as the System Photo Library.
This preserves the library structure instead of attempting to reconstruct Apple’s internal database manually.
Apple provides instructions for moving a Photos library to another disk.
How to Handle WhatsApp on a Clean macOS Installation
WhatsApp should normally be treated differently from an old-fashioned desktop application whose entire history lives exclusively on the Mac.
The current Mac application functions as a linked device associated with the primary WhatsApp account.
For a clean macOS installation, the safer approach is generally:
- Install the current version of WhatsApp.
- Link the Mac to the existing WhatsApp account again.
- Allow the application to synchronize its supported history.
Copying old WhatsApp containers or Application Support directories from an older macOS installation is usually unnecessary and can bring old caches, databases and application state into the new system.
If a particular locally stored attachment is important, preserve the old disk until the new application has been verified.
What Should You Do With 100+ Folders in Application Support?
Do not copy the entire Application Support folder manually.
That would recreate many of the same problems that a clean installation is intended to eliminate.
~/Library/Application Support is a shared storage area used by many applications. Some folders may contain essential user databases. Others may contain caches, indexes, download state, old versions, support processes or data from applications that have not been installed for years.
The better approach is application-by-application recovery.
Use This Decision Process for Every Important Application
- Does the application sync its data through an account or cloud service?
If yes, reinstall it and sign in first. - Does the application have an Export or Backup command?
If yes, use the application’s own export mechanism. - Does the application store ordinary documents?
Move the documents, not the Library support files. - Does it maintain a unique local database?
Check the application’s migration procedure before copying anything. - Is the application no longer needed?
Do not migrate its data.
This process takes longer initially, but it produces a significantly cleaner system.
What About ~/Library/MobileSync?
MobileSync commonly contains local iPhone and iPad backups. On a long-running Mac it can account for tens or even hundreds of gigabytes.
Before moving it, ask a simple question:
Are these old device backups still needed?
If current devices are backed up elsewhere and the historical backups have no recovery value, they do not need to become part of the new Sequoia installation.
If they are important, preserve them separately until the new Mac environment is completely verified.
A clean install is a particularly good opportunity to stop automatically carrying old device backups from one Mac installation to the next.
Which Applications Are Most Likely to Cause Problems?
The biggest migration problems are usually not ordinary self-contained applications. They are applications that install components outside their own application bundle or depend heavily on system permissions.
Applications in the following categories should generally be reinstalled from current installers rather than copied from Ventura:
- VPN clients,
- antivirus and endpoint security software,
- firewalls and network filters,
- virtualization software,
- audio interfaces and audio drivers,
- printer and scanner software,
- backup utilities,
- filesystem drivers,
- NTFS or other third-party disk drivers,
- hardware control utilities,
- system monitoring utilities,
- applications using system extensions,
- applications using background services or privileged helpers,
- older menu bar utilities,
- developer environments with extensive command-line components.
These applications can depend on files in several system and user locations simultaneously. Copying only the application bundle may leave them incomplete, while migrating every related support file can reintroduce obsolete components.
A fresh installer built for current macOS versions is usually the better solution.
Which Applications Are Usually Easier?
Applications whose important data is synchronized through an online account are usually much easier to restore cleanly.
Typical examples include:
- modern browsers with profile synchronization,
- cloud storage applications,
- password managers with synchronized vaults,
- note-taking applications using cloud storage,
- subscription applications with server-based settings,
- communication applications based on online accounts.
Install the latest version, sign in and verify the synchronized data before copying anything from the old Library.
Installing macOS Sequoia on an External Thunderbolt SSD on a 2018 Mac mini
The 2018 Mac mini is officially compatible with macOS Sequoia. It can also use a properly configured external storage device as a macOS startup disk.
A fast NVMe or blade SSD connected through Thunderbolt can provide substantially different storage performance characteristics from an older SATA SSD.
For a modern macOS SSD startup volume, APFS is the appropriate filesystem.
Important: The 2018 Mac mini Has the Apple T2 Security Chip
External startup media can therefore be affected by Startup Security Utility.
If the Mac refuses to start from the new external SSD, boot into macOS Recovery and check:
Utilities > Startup Security Utility > Allowed Boot Media
The option allowing booting from external or removable media may need to be enabled.
This does not mean Secure Boot has to be disabled completely. External boot permission and Secure Boot policy are separate settings on T2-equipped Intel Macs.
Apple describes the current process in its guide to using external storage as a Mac startup disk.
Recommended Ventura-to-Sequoia Migration Process
For a heavily used Mac with many years of accumulated user data, the following sequence provides a good balance between cleanliness and safety.
1. Make a Real Backup First
Keeping the old startup disk untouched is useful, but it should not be the only backup.
A disk can fail independently of a migration.
Create a current backup of important data before making changes. Time Machine is particularly useful because it preserves historical versions of changed files rather than providing only one current snapshot.
2. Leave the Ventura SSD Unchanged
Do not erase it after Sequoia starts successfully.
Keep it as a frozen reference environment until the new installation has been used long enough to reveal anything that was forgotten.
This is especially valuable for obscure application databases that may not be missed immediately.
3. Install Sequoia Cleanly on the New SSD
Format the destination appropriately and install macOS Sequoia without cloning the existing Ventura system.
Boot into the new Sequoia installation and verify that basic hardware, networking and external storage behave normally.
4. Create a Fresh User Account
If the objective is maximum cleanliness, avoid immediately restoring the entire historical account.
Create a new account and let Sequoia generate a fresh home directory and a fresh ~/Library.
5. Sign Into the Apple Account
Enable the iCloud services that are already used, such as:
- iCloud Drive,
- Passwords and Keychain,
- Contacts,
- Calendars,
- Notes,
- Safari synchronization,
- Messages in iCloud,
- iCloud Photos.
Allow synchronization to complete before manually importing equivalent old data. This avoids unnecessary duplicates.
6. Reinstall Applications Manually
Download current installers from trusted sources or the App Store.
Start with applications used every day. There is little reason to reinstall 100 applications simply because they existed on the old disk.
7. Copy Ordinary Personal Files
Move clearly understandable content such as:
- Documents,
- project folders,
- Desktop files that are still needed,
- Downloads worth preserving,
- music files,
- video files,
- archives,
- source code and development projects.
8. Handle Database-Based Applications Separately
Mail, Messages, Photos and other database-driven applications deserve individual migration procedures.
Do not treat them as ordinary folders.
9. Recover Application Support Only When Something Is Missing
After installing and opening an application, determine whether its data returned through synchronization or whether it needs a local database from the old disk.
Only then investigate the relevant Application Support, Containers or Group Containers directory.
This reverses the usual migration logic:
Instead of copying everything and deleting what causes problems, copy nothing and restore only what proves necessary.
10. Keep the Old Installation for a While
A forgotten application may not be opened until weeks after the migration.
A rarely used local mailbox might not be noticed immediately.
An old software license or project database may become important months later.
Keeping the Ventura SSD unchanged provides an excellent safety net.
The Snapshot Problem: Avoid Overwriting New Data With Old Data
One of the most dangerous situations occurs after the new system has already been used for several days.
Suppose an application begins creating new data on Monday. On Friday, an old application database from the Ventura disk is copied over the new database.
The result can be:
- new data disappearing,
- old data replacing current state,
- database corruption,
- sync conflicts,
- duplicate records.
This is why delayed manual replacement of Library folders should be approached carefully.
When possible, use:
- application import functions,
- cloud synchronization,
- database merge tools supplied by the application,
- separate exported archives.
If direct file replacement is unavoidable, back up the new data before replacing it with anything from the old disk.
Should You Use Migration Assistant at All?
Yes. Migration Assistant remains extremely useful. The question is whether it should migrate the entire historical environment.
There are three reasonable strategies.
| Strategy | Advantages | Disadvantages |
|---|---|---|
| Full Migration Assistant transfer | Fast, convenient, preserves most user state | Can bring years of old settings and application data |
| Completely manual migration | Cleanest possible installation | Time-consuming and easy to overlook obscure local data |
| Selective migration | Good balance of cleanliness and data preservation | Requires some planning |
For an account that has been continuously migrated for many years, selective migration is usually the most attractive approach.
What Should Not Be Copied From the Old Library Without a Reason?
Avoid treating these directories as generic backup-and-restore folders:
- Application Support
- Caches
- Containers
- Group Containers
- Preferences
- Saved Application State
- LaunchAgents
There are legitimate reasons to recover individual items from all of them. The key word is individual.
The objective of a clean installation is defeated if the complete contents of an old Library are dropped on top of the newly generated one.
Why Do Mail, Messages and Photos Use So Many Strange Files and Folders?
Mail, Messages and Photos are not designed as human-readable folder archives.
They are applications backed by databases, indexes, metadata stores, attachment stores and internal identifiers.
The seemingly random directory and file names are not an indication that the data is damaged. They are implementation details used by the applications.
This is why moving the supported logical unit is preferable to manually rearranging internal files:
- export a Mail mailbox,
- synchronize Messages through iCloud,
- copy a complete Photos Library package,
- export data from third-party applications using their own tools.
Frequently Asked Questions
Does Mac mini 2018 support macOS Sequoia?
Yes. Apple officially lists the 2018 Mac mini as compatible with macOS Sequoia.
Can macOS Sequoia run from an external Thunderbolt SSD?
Yes. macOS can be installed on compatible external storage and used as a startup disk. On a 2018 Mac mini, the T2 security settings must also permit booting from external media.
Should an old Ventura user account be migrated completely?
Not necessarily. For a user account that has accumulated many years of applications and settings, a fresh Sequoia account followed by selective data migration can result in a cleaner system.
Does Migration Assistant copy the User Library?
User-specific application state forms part of the broader user environment. Migration Assistant can migrate user accounts and lets users select categories within them, but it does not expose every individual folder inside ~/Library as a separate migration option.
Is Application Support copied only for applications selected in Migration Assistant?
It should not be assumed that deselecting an application automatically removes every associated item from the migrated user’s Library. Applications and user accounts are separate Migration Assistant categories.
Should the entire Application Support folder be copied manually?
No. For a clean installation, restore application-specific data only when an application actually requires it.
What is the safest way to migrate Apple Mail?
Allow server-based IMAP, Exchange and iCloud accounts to synchronize again. Export and import mailboxes that exist only locally.
What is the safest way to migrate Messages?
When possible, enable Messages in iCloud on the old installation, allow synchronization to finish and enable the same service on Sequoia.
Should a Photos Library be opened and its folders copied manually?
No. Copy the Photos Library as a complete package, then open that library in Photos. If iCloud Photos is enabled, synchronization may provide an even simpler migration route.
Should applications be migrated or reinstalled?
For a truly clean installation, reinstall current versions of important applications. This is particularly important for VPN software, security tools, hardware drivers, virtualization software, network filters and applications that install system-level components.
How long should the old Ventura disk be kept?
There is no universal period, but it is sensible to keep it unchanged until every important application, archive, mailbox, photo library and project has been verified on Sequoia. For a Mac containing many years of history, that may mean keeping the old disk for several months.
Final Recommendation
Moving from Ventura to Sequoia is an ideal opportunity to break the cycle of endlessly migrating the same macOS user environment from one installation to another.
For a 2018 Mac mini moving from an older SATA SSD to a faster Thunderbolt SSD, the most balanced approach is:
- Install Sequoia cleanly.
- Create a fresh user account.
- Keep the Ventura disk unchanged.
- Make an independent backup.
- Let iCloud and server-based services restore synchronized data.
- Reinstall current versions of applications.
- Move ordinary documents manually.
- Handle Mail, Messages, Photos and other databases individually.
- Recover old Library data only when a specific application actually needs it.
This takes more work than pressing “migrate everything,” but it preserves the main benefit of a clean installation: a modern macOS environment without automatically importing every piece of software history accumulated over the previous decade.
For more practical Mac maintenance and troubleshooting information, browse the latest macOS troubleshooting guides.