Step 1: Export from Funraisin · MS Gong Ride Setup

Goal: get every order out of Funraisin as a CSV that Shopify can understand.

Funraisin can produce a report already shaped in Shopify's import format, with the product and variant IDs resolved for you. This is the only export you should use. Do not build your own column layout.

Steps

Log in to the Funraisin admin for your event and go to Reporting, then Data Exports.
Look for an existing Shopify-format export for your event. On Gong Ride this is export id 217, named GONG - Funraisin Shop Orders. It has 51 columns and is set to the full event date range.
If your event has one, open it and use the manual download button.
If your event does not have one, create it: copy the Gong export's field layout, set the date range to cover your whole event, and save it. This is a one-time job per event.
Save the file somewhere you will find it again. Name it with the date you pulled it.

Note

The manual download ignores the "New Records Only" setting. It gives you every order in the date range, every time. That is what you want, because it means you always have a complete picture. Step 2 is where you narrow it down to what has not been imported yet.

Key columns

Column	What it is
Name	The Funraisin order reference, for example GONGS149458. One order can span several rows.
Email	The buyer. Used to match or create the Shopify customer.
Product ID	The Shopify product this line item maps to.
Variant ID	The Shopify variant, meaning the specific size and colour.
Quantity	How many of that item.
Financial Status	Only import rows that are paid.
Shipping fields	Name, address, suburb, state, postcode, country, phone.

One row is one line item. A buyer who ordered a tee, a ticket and socks appears as three rows sharing the same Name.

Watch out for

Do not use the Funraisin /sales or /transactions API endpoints. They cap at 1000 rows, oldest first, and ignore paging and date filters. They also carry no line-item detail. They cannot build orders. The report export is the only reliable source.
Check the row count looks sane before you go further. If a report that normally returns thousands of rows suddenly returns a few hundred, something is wrong with the export, not with your event. Stop and investigate rather than importing a partial file.