How to Set a Custom Sync Start Date

Choose a sync start date when you want a new connection to import transactions from a set day. For example, use January 1, 2025 when you are bringing a new year's records into Cryptoworth.

The date controls which history the connection imports. A Date filter in Transactions only changes which imported records you see.

Use a custom date only when you have a plan for any assets held before that date. A later start can leave out purchases, deposits, and incoming transfers needed for inventory and cost basis.

For example, if you held 2 ETH on January 1 and sold it in February, the calculation still needs the acquisition cost of that ETH. A start date does not create that cost basis.

Keep the earlier history, or use reviewed opening balances under your accounting policy. Do not import the same holdings through both methods. See Setting Up Bookkeeping from a Specific Date.

Cryptoworth warns that a custom start date can cause reconciliation gaps. If you need complete history, leave the custom date option off or the start-date field blank.

Use the supported connections list below to check your exact connector name.

Open the entity you want to work in. Go to Integrations > Connections, then click the + button to open Connect.

Click Add wallet to open the catalog for wallets, blockchains, exchanges, and custody accounts.

Choose the path for your connection: blockchain wallet, Bitget, or Gemini.

These steps use Ethereum (ETH) as an example. Other supported blockchain forms use the Custom Date option too.

Choose Blockchains. Search for the network, then select the exact catalog entry for your wallet.

Enter a wallet name and its public address. Keep Sync Transactions checked.

Use the public address for the selected network. Never enter a private key or seed phrase.

Check Custom Date and read the reconciliation warning. Click the calendar button beside the date field.

Choose the year, month, and day in the calendar. This example uses January 1, 2025.

Check the date, public address, and sync settings. Click Connect when they are correct.

In the connection catalog, choose Exchanges & Custody. Search for Bitget and select its card.

Name the connection. Enter the API Key, API Secret, and API Passphrase from your dedicated, read-only Bitget API key.

For key setup, see BitGet: How to Generate a Read-Only API Key Pair.

Keep Sync Transactions checked. Check Custom Date, read the warning, then open the calendar.

Select the year, month, and day you want to start importing.

Review the date and account details. Click Connect after you have entered the correct read-only API credentials.

Gemini uses a Sync transactions from field. It does not use the Custom Date checkbox shown in the wallet and Bitget examples.

In Exchanges & Custody, search for Gemini and select its card.

Name the connection and enter your read-only API Key and API Secret. Locate Sync transactions from below these fields.

Enter your start date in Sync transactions from. Keep Sync Transactions checked, review the details, then click Connect.

Leave the date blank if you want Gemini to sync from the beginning of its available history.

Return to Integrations > Connections. Check the connection's Status and wait for its transaction sync to finish.

Balance Synced is a balance-only status. It does not confirm that transaction history was imported. The example below shows where completed connections display Synced.

Go to Subledger > Reconciliation. Click Sync & Reconcile to refresh the checks. When it finishes, open Data Sanity Check.

Expand a connection marked Gaps detected. Compare Calculated Balance with Reported Balance for each affected asset.

A completed sync does not prove that the accounting history is complete. Check that holdings at the start date have the right quantity and cost basis. Resolve missing history or opening-balance issues before relying on a calculation.

If a later disposal shows Missing Inventory, check for acquisitions or transfers before the sync start date. See How to Resolve Transaction Deviations.

The lists below reflect the new-connection forms available on November 1, 2026. Use the exact catalog name. Support can differ between related networks and between mainnets and testnets.

Each connector below shows a Custom Date checkbox.

Deribit does not currently show a start-date control in its new-connection form. Some older instructions describe one. Use the controls shown in the current form.

Other exchange and custody forms checked on this date did not show a start-date control. The separate Nibiru (NIBI) and XAI (XAI) blockchain entries were unavailable, so their setup controls could not be checked.

For the full catalog check, see Connection_Start_Date_Support.csv.

Why can't I see Custom Date?

Check the exact connector in the support list. Gemini uses Sync transactions from instead. A related chain with a similar name may have different controls. For example, Arbitrum (ETH) and Arbitrum Nova (ETH) show Custom Date; the separate Arbitrum One (ETH) entry does not.

Does a later start date remove transactions already imported?

Do not use this setup option to remove existing records. These steps apply when adding a new connection. A Transactions date filter also leaves the underlying records in place.

Will I get all history after my chosen date?

The source still controls which records its API can return. Check the imported coverage and use an approved import method for any gaps. A custom date cannot recover records that the source does not provide.

Should I use a later date to fix missing inventory?

No. Find the missing acquisition, transfer, or reviewed opening balance. Moving the start date forward can omit more of the history needed for cost basis.