Bring existing records with you
Import Your Collection into Collectaneum
Moving to structured collection management should not mean abandoning years of work. Existing spreadsheets can contain valuable identity, acquisition, condition, provenance, valuation and location information, even when that information has become inconsistent or difficult to use.
The aim of an import is therefore not merely to transfer rows. It is to preserve what is useful, understand what each field means and begin turning a flat inventory into connected collection records that can be reviewed and improved over time.
Importing is a migration, not a copy-and-paste exercise
A spreadsheet row may combine several different ideas: the general product, the edition, the particular example you own, its condition, where it came from and what it may be worth. Transferring every cell unchanged can preserve the original confusion as easily as it preserves the original information.
A stronger migration separates those meanings carefully. It keeps the source available, maps information into the appropriate part of the registry and leaves uncertainty visible where the source cannot support a stronger conclusion.
Understand what you already have
Review the spreadsheet, workbook or export before changing it. Identify which columns describe collections, products, variants, owned items, condition, provenance, value, location and notes.
Separate useful data from historical clutter
Preserve information that still explains the object, but distinguish current facts from abandoned categories, duplicate rows, temporary notes and values whose date or purpose is no longer known.
Map the old structure to the new one
Decide which source columns belong to shared product information and which belong to the individual example you own. This is where a flat list begins to become a connected registry.
Import in a manageable stage
Move one collection, category or representative sample first where appropriate. A staged import makes it easier to test assumptions before repeating them across the full collection.
Review the result against the source
Check object counts, identities, variants, values, dates, locations and notes after import. The source should remain available until the new records have been validated.
Enrich the record over time
Add photographs, documents, provenance, condition detail and better classification when those improvements become useful. Migration does not require every record to be perfected immediately.
What usually needs attention before import
Most collection spreadsheets are not “bad data.” They are records built gradually for the needs of one collector. The challenge is making their meaning explicit enough for a structured system and for another person to understand later.
Several ideas share one column
A field such as “edition” may actually contain publisher, date, printing, packaging and variant information. Import preparation should separate those meanings where the distinction matters.
The same value appears in several forms
Names, dates, condition labels and locations often vary through spelling, abbreviations or changing habits. Normalisation improves search and reporting, but the original wording may still deserve preservation.
Rows describe products inconsistently
One row may identify a general product while another describes a very specific owned example. A structured system needs to know which information is shared and which is object-specific.
Historical values have lost their context
A price may represent purchase cost, insurance value, market estimate or asking price. Figures should not be imported as equivalent when their purpose and date differ.
Images and documents sit outside the spreadsheet
Files may be organised by filenames, folders or links that only the original collector understands. The migration plan should decide how evidence will be reconnected to the correct object.
Duplicates may not be true duplicates
Two similar rows might represent accidental duplication, multiple copies, different variants or the same object recorded at different times. Deletion should follow review rather than assumption.
Start with the record you have
You do not need to perfect everything before moving
Waiting for a completely cleaned and standardised spreadsheet can turn migration into an endless preliminary project. It is often more useful to preserve the existing information, resolve the most important structural questions and improve individual records after they are in a system designed to support that work.
The appropriate level of preparation depends on the source. A small, consistent workbook may need little intervention. A long-lived file containing several collecting systems, changing terminology and thousands of images may justify a more deliberate staged approach.
Keep during import
- →Existing object names and identifiers
- →Collection and category information
- →Acquisition dates and costs
- →Condition notes
- →Known provenance
- →Current locations
- →Valuation evidence and dates
- →Source references and useful free-text notes
Improve after import
- →Inconsistent naming
- →Unclear edition and variant distinctions
- →Mixed date formats
- →Broad condition descriptions
- →Missing photographs
- →Unsupported provenance claims
- →Values without a stated purpose
- →Temporary or inherited classification systems
Principles for a safer migration
Import work is most reliable when it protects the source, makes transformations visible and treats uncertainty as information rather than an inconvenience to be removed.
Preserve before you simplify
Do not discard source information merely because it does not yet fit the new structure. Retain uncertain or unmapped material until its meaning has been reviewed.
Structure where structure adds value
Consistency improves search, comparison and reporting, but not every note should become a field. Some information is more honest and useful as qualified narrative.
Do not convert uncertainty into certainty
An ambiguous spreadsheet entry should remain ambiguous after import. Migration should not silently turn a tentative attribution, estimated date or inherited story into a confirmed fact.
Validate before retiring the source
Keep the original workbook and an untouched backup until the imported records have been checked. Migration is complete only when the new system can be trusted.
What the first useful imported record looks like
The first version does not need to contain every possible detail. A useful imported item may begin with a reliable identity, its collection, an acquisition date, a location, basic condition, an existing reference and any important uncertainty carried over from the source.
Photographs, supporting files, detailed provenance, grading history, valuation context and refined classification can be added where they improve the record. This preserves momentum without pretending incomplete evidence is complete.
Preserve the work already done
Move the collection, then make the record stronger
An import should reduce re-entry, protect useful history and create a practical route toward greater consistency. The goal is not a dramatic one-day conversion. It is a controlled transition from personal tracking to a registry that can support deeper knowledge, search, reporting and long-term stewardship.