Can you migrate our data without downtime?
Often, using the add-before-remove approach above, depending on the engine, the size of the data and how many systems write to it. Some moves do need a short window. If yours does, you'll know how long and why before the date is set.
Is a database developer different from hiring a backend developer?
Yes, in focus. A backend developer builds the server side that uses the database. Database work is about the data itself: how it's structured, how fast it answers, the rules that keep it correct, and moving it safely. Many projects need both, and n-frames covers both.
What if we're not sure the database is actually the bottleneck?
That's common, and finding out comes first. We time the slow screens, look at what queries they send and read the query plans. Sometimes the fix is an index, sometimes it's the app's code, and sometimes it's the server it runs on.
How do we know our backups actually work?
Only by restoring one. Restore a recent backup onto a separate server, check the newest records are there, and time it. Do it again after any big change to the database or the hosting.
We've outgrown a spreadsheet or an Access database. Is that database work?
Yes, and it's one of the most common versions of it. The data moves into a proper database with rules that stop the duplicates and blanks a spreadsheet allows, usually with simple screens on top so the team keeps working the way it's used to. If the data sits on a cloud host, AWS developer covers that side.