Last updated: November 13, 2026
Key Takeaways
- Save the workspace settings, project list, keyword set, report plan, and user access before the change starts.
- Record the workspace structure, project details, keyword list, and access settings in one session.
- Write down how projects, keyword sets, and report rules fit together, not just how the screen looks today.
- Save every term, group, and tag relationship before the workspace change starts.
Back up your Ranknar.com settings before a workspace change by saving the workspace checklist, project inventory, keyword set, report export plan, and user access list before anything moves. This guide to how to back up Ranknar.com settings before a workspace change starts with one dated folder. Do it before the switch. The steps below show what to save, what to review, and what to keep for a clean rollback.
What you need to save first in Ranknar.com

You need to save the workspace settings, project list, keyword set, report plan, and user access before the change starts. That gives you a paper trail for the exact setup that exists today, not the version you wish you had after the move.
Picture this: you are about to move a workspace, and three days later someone asks why a project vanished, why a keyword group looks different, or why a report no longer matches the old view. A backup file or written export plan makes that question answerable in minutes, not hours. Use one folder, one date, and one naming style.
Keep the backup set in a place you can reach without logging into the workspace itself. A shared drive, a local encrypted folder, or a controlled team vault all work better than a note buried in email. One dated folder is enough if it contains the right pieces.
Save these items before you touch the workspace:
- Workspace name and current purpose
- Project names and their folder order
- Keyword sets and tag groups
- Report names, schedules, and filters
- User access roles and owner names
If the workspace change includes a team handoff, this list matters even more. The new owner can recreate structure faster when the old structure is written down clearly. If the handoff is sensitive, it can help to review the plan with a qualified administrator or consultant and follow internal policy.
How do I back up Ranknar.com settings before a workspace change?
You back up Ranknar.com settings by recording the workspace structure, copying project details, exporting the keyword list, and writing down report and access settings in the same session. A 4-part record is a practical baseline before permissions or project placement changes.
Start with a clean checklist. Then follow the steps in order so you do not miss a setting that only shows up once.
- Open Ranknar.com and review the current workspace overview. Save the workspace name, project count, and any folder labels that define the current setup.
- List each project and note its position, tag groups, and any linked keywords. This gives you the full project inventory before the move changes the layout.
- Capture the keyword set for each project and store it in your backup folder. Keep the terms grouped the same way they appear now so you can rebuild them later.
- Record report names, date ranges, filters, and delivery schedules. That tells you which reports need to be rebuilt after the workspace change.
- Review user access and write down who has owner, admin, or standard access. This can help prevent a handoff problem when the workspace changes hands; if the transfer is complex, consult a professional or follow your organization’s access policy.
- Store the backup in a dated file name, such as
Ranknar-workspace-backup-YYYY-MM-DD. That makes the last known version easy to find.
Here’s the catch: a backup is weak if it only contains screenshots. Screenshots help, but they do not sort cleanly and they miss structure. Use written notes, exports where available, and a clear file name together.
Save the workspace structure, not just the screen
You save the workspace structure by writing down how projects, keyword sets, and report rules fit together, not just how the screen looks today. The structure is the part that saves time later, especially when a workspace contains more than one project group.
Picture this: your workspace has a neat order now, but the new workspace drops folders into a different layout. If you only kept screenshots, you still have to guess which project belongs where. A structure note keeps the order intact.
Write these details in plain text or a spreadsheet:
- Workspace name
- Project order
- Folder names
- Tag names
- Keyword set names
- Report names
- Access roles
A spreadsheet works well because you can sort, filter, and compare later. One tab for projects, one tab for keywords, and one tab for reports is usually enough. If you prefer a document, use short headings and bullet points so the next person can scan it fast.
Do not mix old and new structure in the same list. That causes the most common backup error: a user sees one folder title and assumes it already exists in the new workspace. Keep the current state separate from the planned state. Separate tabs avoid that mess.
If Ranknar.com lets you export any of these lists directly, save the exported file and keep your own written notes beside it. Exports are machine-friendly. Notes explain why the structure exists.
Back up the keyword set before the move
You back up the keyword set by saving every term, group, and tag relationship before the workspace change starts. That is the part most teams regret skipping, because keyword groups are easy to rebuild badly and hard to audit later.
Picture this: the workspace is changing, but your rankings plan still depends on the same keyword buckets. If a group gets renamed or split during the move, your reports can stop matching the old structure. A full keyword backup gives you the map.
Use a list with these fields:
- Keyword
- Project name
- Group or tag
- Current status label
- Notes for special cases
If your keyword set is large, split it by project first and then by group. That keeps the backup readable when you return to it later. A long, flat list looks complete but often hides the exact grouping that matters most.
A useful habit is to mark any keyword that belongs to more than one report. Those keywords are the ones most likely to cause confusion after the workspace changes. The same term can look fine in one project and out of place in another.
Do not rely on memory for keyword groups. Even a small workspace can change enough during a handoff to make the old grouping hard to reconstruct. One extra column for notes can save you from that mistake.
Check report export planning before anything changes
You check report export planning by deciding which reports need a saved copy, which ones need scheduled reruns, and which ones only need their filters written down. That plan matters because report history often gets messy when a workspace changes.
Picture this: a manager asks for last month’s view after the move, but the schedule now points to a new workspace and the old filter set is gone. If you planned the backup, that report still has a trail. If you did not, you start over.
Build your report plan around these three categories:
- Reports that need a saved copy now
- Reports that can be recreated from written settings
- Reports that should stop before the workspace switch
For each report, record the name, date range, sort order, filters, and delivery method. If the report is tied to a client, campaign, or channel, write that down too. A report without context is hard to trust later.
The most common mistake is backing up only the final output and skipping the settings behind it. That costs time because the output alone does not show how the report was built. Save both if you can. If not, save the settings first.
A simple folder with Reports, Keywords, Projects, and Access subfolders works well. Keep the report files in the same dated backup so nobody has to hunt for them later. Google’s backup guidance also emphasizes organized copies and recovery planning; see Google Workspace Admin Help and the National Institute of Standards and Technology (NIST) backup recommendations.
Review user access before the workspace changes
You review user access by listing every person who can open the workspace, then checking what role each person has before the change. That step protects the handoff, the ownership record, and the cleanup after the move.
Picture this: a workspace change happens, and an old admin still has access while a new teammate cannot find the projects they need. That kind of mismatch creates delay fast. A pre-change access review keeps the next step clean.
Write down:
- User name
- Email address or login label
- Role
- Workspace-level access
- Project-level access
- Owner or backup owner
If you see shared accounts, flag them in your notes. Shared logins make it harder to tell who changed what, and they make the backup record less useful later. A named user list is better than a guess.
Do not change access and backup at the same time unless the workspace change requires it. First capture the current state. Then make the access change. If you reverse that order, you lose the exact record you were trying to preserve.
This is also the place to decide who needs a copy of the backup file. Keep that list small. One or two controlled people are usually enough for a workspace handoff. More copies mean more places for old settings to drift.
A clean backup file name and folder plan saves time
A clean backup file name and folder plan saves time because the next person can find the right version in under a minute. That matters when you have more than one workspace change in a month.
Picture this: you make three backup files in a week, and each one is called “final” or “updated.” By Friday, none of them tells you which workspace it belongs to. A date and project name solve that problem immediately.
Use this pattern:
Ranknar- workspace name
- change date
- backup type
Example structure:
Ranknar-ContentOps-2026-01-12-workspace-backupRanknar-ContentOps-2026-01-12-project-inventoryRanknar-ContentOps-2026-01-12-user-access
Keep the whole set together in one parent folder. Do not scatter the files across email, chat, and desktop. If you need to share the backup, send a copy, and keep the original copy in place.
If your team has a standard naming rule, follow it. If not, keep it simple and consistent. The goal is speed, not decoration. One folder tree beats six loose attachments every time.
For broader account and workspace planning, the hub on ranknar.com account and workspace operations gives the right parent context without repeating this checklist. Internal guidance on file naming and version control can also help if your team already uses a shared process.
Common mistakes that break a workspace backup
The biggest backup mistake is saving the wrong layer of detail. That leaves you with a file that looks complete but cannot rebuild the workspace later. The fix is to save structure, settings, and access together.
Picture this: the workspace change is done, the dashboard opens, and half the setup is missing because nobody wrote down the filters or project order. The team then spends the next day reconstructing the old setup from memory. That is the expensive version.
Watch for these errors:
- Saving screenshots only, with no text record
- Forgetting project order and tag groups
- Missing one keyword set tied to a secondary report
- Leaving user access off the backup list
- Using a file name with no date
Each mistake costs time in a different way. Screenshots slow down searches. Missing access data slows down handoff. A vague file name makes version control pointless.
Use the same checklist every time. A 10-minute review before the workspace change can save a much longer cleanup afterward. If the workspace is small, the temptation is to skip steps. That is where backup mistakes usually start.
What should I save before changing a Ranknar.com workspace?
You should save the workspace structure, project inventory, keyword set, report settings, and user access before changing a Ranknar.com workspace. That set gives you enough detail to rebuild the old setup or spot what changed.
Save the project list, the keyword groups, the report filters, and the access roles in one dated folder. If you can export any of those items, keep the export and your written notes together so nothing gets lost in the handoff.
Can I preserve project structure when changing workspaces?
Yes, you can preserve project structure if you record the current layout before the move and rebuild from that record after the change. The safest practical record includes folder order, tag names, project names, and the keyword groups attached to each project.
A screenshot alone is not enough if the workspace has multiple projects. A written project inventory gives you the structure in a form that can be checked line by line.
What is the safest way to prepare for a Ranknar.com workspace change?
The safest practical way is to make one dated backup set that covers structure, keywords, reports, and access, then verify it before any workspace setting changes begin. That reduces the chance of losing a project relationship or a report filter during the switch.
Keep the backup in one place, use a clear file name, and separate the current state from the planned state. If you do only one thing, save the project inventory first. That is the record most people need when a workspace change goes wrong.
Drafted with AI; not yet reviewed by a person.