Your website is not only the pages a visitor can see.
Important data may include:
articles
user accounts
customer records
product information
images and video
configuration
analytics exports
email lists
documents
logs
metadata
database relationships
If the service holding that information disappeared tomorrow, what could you recover?
Backup is not the same as export
A backup is a recoverable copy intended to restore information after loss or damage.
An export is information taken out of a system in a usable or transferable format.
A backup may be excellent for restoring the same application while being inconvenient for moving to a different one.
An export may be easy to inspect while leaving out pieces required for a complete disaster recovery.
You may need both.
Archive is another job
An archive preserves material for long-term reference or history.
Archived information may no longer belong in the active application, but that does not make it worthless.
Replica is another job again
A replica is another synchronized or near-synchronized copy used for availability, performance or redundancy.
A replica can faithfully copy accidental deletion or corruption. It should not automatically be treated as the only backup.
Common portable formats
CSV is useful for rows and columns.
JSON is common for structured application data and APIs.
XML remains common in feeds, exports and integrations.
SQL dumps can preserve database structures and records for compatible database systems.
Media and uploaded files may need to be copied separately from database records.
Ask portability questions before you need the answers
Can the important records be exported?
Are IDs preserved?
Are relationships preserved?
Are dates preserved?
Are uploaded files included?
Can another system read the result?
Can the website be reconstructed without the original vendor?
Test recovery
A backup that has never been restored is an assumption.
Critical systems should occasionally prove that their important information can actually be recovered.
Portability does not require rejecting hosted services.
It means knowing how to leave without abandoning the history of the property.
Put This Lesson to Work
Choose a real website or project you control. Identify where this lesson applies, record who is responsible for that part, and identify one change or check you can safely make.
Worked example
For a domain-email lesson, record the separate website and email providers. Look up the existing MX records without changing them, then confirm which provider receives mail.
Your finished result
A short explanation of the system, its owner, and a checked next action. Keep passwords and recovery codes out of your notes.
Check your understanding
- Can you explain the main idea without repeating a slogan?
- What evidence or example supports your explanation?
- Which decision will you make differently, and why?