We’re planning to move a shared business tracker into Busabase, but some colleagues still prefer editing Excel files and sending them back. If both copies remain editable, it could become unclear which version is current. How should we manage the transition and establish the authoritative version? What is a practical process for reviewing and incorporating offline changes without maintaining two competing trackers?
Choose one place as the current record for the part of the work you move. If that is Busabase, keep the old Excel file as a dated archive or export, but stop treating it as a second editable master. Two files that both accept changes will drift even if each looks correct on its own.
Move one real project first: agree on the fields and owner, import a small checked sample, then tell colleagues the Busabase Base is where updates now go. For teammates who must work offline in Excel, ask them to return a clearly dated file with stable record IDs and a note of what changed. Have a person or Agent compare it with the current Base, propose only the differences, and review those changes before they become current; do not overwrite the entire Base from an older spreadsheet. Keep the imported file and decision history so the team can trace a disagreement. What is keeping some colleagues in Excel today: offline access, formulas, or a familiar editing workflow?
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in