How Can I Clone Transactions From Other Workspaces?

It is possible to clone transactions from one source workspace to another destination workspace.

This is a one-way copy from the source workspace to the destination workspace.

You must have full admin permissions to both workspaces to setup the connection.

Main Use Cases
You can use this functionality:

1. For testing purposes
   
1. For example, you can create a test workspace
   
2. You can then clone transactions from a production workspace to your test workspace
   
2. To enable multiple multiple connectors of the same type
   
1. For example, you have multiple QuickBooks tenants
   
2. You can create one workspace per QuickBooks tenant, but "merge" transactions from all tenant into 1 workspace
   

Gather Source Workspace Information
First gather information from the source workspace.

1. Login to the source workspace
2. Type ALT-Q or copy everything after the last slash from the URL
   
1. Copy the source workspace ID
3. Browse to "Transactions > All Transactions"
   
1. Open any sample transaction whose data source you want to clone 
2. On the "Metadata" tab, copy field "Data Source"
   
4. Browse to "Account > My Profile"
   
1. On the "Security" tab, copy the "API key"
   

You should have the following:

1. The source workspace ID
2. The source data source name
3. Your source API key 

Add a Connector in the Destination Workspace

Second add a connection to the destination workspace.

1. Login to the destination workspace
   
2. Browse to "Transactions > Connections"
   
3. Add a connection of type "TransCopy"
   
4. Click on "Save"
   

Add Transactions

Third add transactions to the destination workspace.

1. Login to the destination workspace
   
2. Browse to "Transactions > Add Transactions"
   
3. Select "TransCopy" as the data source to import transactions from
   
4. Provide information gathered in the first step
   
5. Continue to map fields and finish the import

Mapping Fields

We recommend that you map field [SC - Unique ID] to the [Unique ID] category:

Even if multiple workspaces have records with the same unique ID, this field will have different values - example:

1. Ex: you synchronize transactions from 2 source workspaces
2. In each source workspace, there is a record with unique ID "123" - but they represent different records
3. Field [SC - Unique ID] will be set to different values for each record
   

• Related Articles

• How Can I See Which Workspaces I Have Access To?

  Here are the steps to view all workspaces you have access to: Login to your workspace On the left pane, click on "My Account > My Workspaces" You can also view the workspaces you are managing using the following steps: Login to your workspace On the ...

• Error - Can't Date Transactions

  Applicability This error applies to the following situation: You are importing transactions You do not have any field mapped to category "Transaction Date" Impact This error prevents you from importing transactions. Explanations Without a field ...

• Error - Can't Credit Transactions

  Applicability This error applies to the following situation: You are importing transactions You do not have any field mapped to category "Owner / Sold By" You do not have any field mapped to category "Territory or Team" Impact This error prevents you ...

• Best Practice - Searching Transactions

  To search for transactions, browse to Transactions > All Transactions. Searching Efficiently Here are some key controls we will discuss: If you have thousands of records, consider narrowing the scope of your search. Specify a date range Ex: this ...

• Error - Unable To Perform A Realistic Simulation Due To An Insufficient Number Of Available Matching Transactions

  Applicability This error applies to the following situation: You are running a calculation using simulation You have a limited number of transactions available Impact This error prevents you from completing a simulation. Explanations There aren't ...