
Choose a clear starting point
Decide whether you are moving an independent dealer’s stock, an antique centre’s sales records, or both. These are related but different records. A stock row describes an item; a sales row describes a transaction. Keep the two purposes clear when preparing files.
Choose a cutover date and record which system is responsible before and after it. List the opening stock, unpaid rent or other balances you need to carry forward. Do not assume a new system should receive every old file just because it exists.
Keep an untouched original
Save a dated copy of every source spreadsheet and its supporting documents. Work on copies during cleaning and testing. Keep a short change log so that a corrected dealer code or date can be traced back to the original record.
Identify which files are authoritative. If a counter book, a monthly sheet and a statement disagree, resolve the difference before importing. Carrying a discrepancy into a new database makes it harder to understand; it does not remove it.
Make identifiers consistent
Agree one format for dealer codes or stock numbers. Check spaces, leading zeros, duplicated codes and names used in place of codes. Do not merge two dealers or two items simply because their descriptions look similar.
Separate active dealers from historical records. An old dealer may need to remain attached to past sales without appearing as a current trader. For independent stock, keep the original item number where possible so photographs and purchase records can still be matched.
Clean dates and amounts
Use explicit dates including the year. A value such as “03/04” can be misunderstood when a file moves between systems. Check how your export handles dates, decimal separators, currency symbols and blank cells.
Keep sale amount, commission, rent and payment method in separate fields where the destination supports them. Do not treat an empty amount as zero without checking what the empty cell means. Review refunds, negative amounts and totals rows so they are not accidentally imported as ordinary sales.
Run a small, representative trial
Ask for the destination’s actual import template and map each source column to it. A system accepting a file is not proof that each field has landed correctly. Begin with an authorised test batch that includes ordinary rows and awkward cases.
For a centre, try several dealers, different payment methods and a month boundary. For a dealer, try available and sold items, restoration costs and incomplete research notes. Check whether re-uploading the same file creates duplicates before repeating a batch.
Reconcile before you switch
Compare the imported row count and totals with the source. For a hypothetical batch of 50 sales totalling £4,250, the destination should explain the same 50 sales and £4,250 before you apply separate commission or rent rules. Break the check down by dealer and payment method to locate differences.
Inspect individual records too. A correct grand total can hide one sale allocated to the wrong dealer. Generate a sample statement or invoice and check dates, descriptions and calculations. Keep the old system readable until the first complete reporting period has been reconciled.
Make the new routine easier to follow
Give the team a short checklist for recording a purchase or sale, correcting a mistake and closing a day. Assign someone to answer questions during the changeover. Review the first week for missing fields and duplicated work.
Explore Antique Pilot for antique centres or Solo for independent dealers. Both are in development ahead of January 2027. Ask which imports and fields are supported for your records before planning a migration; an import capability is not a promise that every spreadsheet format transfers automatically.
Examples are illustrative. Product features and launch availability will be confirmed as testing progresses.
Talk to us about testing ↗