Inventory before mapping
Count the items, identify their original sources and separate text, video and associated permission records. Some material may be a private email compliment rather than a testimonial approved for public reuse. Keep that distinction during migration. Do not treat the fact that a file is in a shared folder as evidence that every item can be published.
Use a small controlled sample
Boast’s documented import process includes assigning a form, mapping fields, setting tags and status, then reviewing the import. Plan a small authorized sample that includes missing fields and a held item. Verify the result before moving a large library. These are suggested checks, not a merchant trial that we have performed or permission to upload real customer data here.
Do not upgrade permission by mapping
A destination field may look convenient but carry a different meaning from the source. If permission evidence cannot be mapped faithfully, retain it separately and keep publication on hold until the responsible reviewer can establish the relationship. An import status should not turn unknown permission into full consent just to avoid an incomplete row.
Reconcile content and public locations
After an authorized migration, compare identifiers, versions and intended destinations. Detect duplicates before sending new requests or displaying the same story repeatedly. Keep the previous library intact until the transfer and recovery record are verified. A record count match alone does not prove that video files, attribution or permission context survived; inspect representative examples of each type.
An original decision example
Illustrative sample: import one approved text item, one video with separate permission evidence and one unresolved historical email compliment. Verify that the destination preserves their different treatment. If all three become publicly eligible by default, stop the migration and correct the mapping before processing the remaining library.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Boast response import process — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast consent states and agreed terms — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Testimonial.to CSV and media export — Merchant documentation · help.testimonial.to · Merchant-controlled · checked 2026-09-24