This document summarizes what to expect when utilizing our sandbox program before going to a product environment. Please review the following use cases and notices to learn more about the experience when moving from one financial account integration to another.
Moving from one account to another could be done for several reasons. This might be done when moving from one accounting platform to another, for example: moving from QuickBooks to Sage, or Sage to QuickBooks. This might be done when moving from one account or data instance to another within a given accounting platform. An example of that might be to start on a sandbox account for testing before moving to production.
Time between accounts
After disconnecting the first account, we will need to clear the mapping associated with linked components within RedTeam Flex. Typically this is done in around 24-48 hours. Once the account mapping is clear. We can link the new account as a fresh integration connection.
Some data may remain within RedTeam from the original integration. Depending on the situation, they may be linked to an equivalent in the new accounting integration. For example, vendors and job costs imported from the first account will continue to exist within RedTeam.
Connecting the new integration account
The new integration account will need to be configured and connected in the same fashion as the original account. This will add several days to the typical interaction timeline to make sure the second integration account is properly connected and that all of the entities are properly connected between the two systems.
Vendors and customers
Any companies in the original integration account and linked with RedTeam will remain afterwards as unlinked companies. Afterward it may be as simple as linking them again, if they exist in the new integration account. Ultimately, how they interact with the new integration account will depend on whether or not there is an equivalent in that account.
These are the different options to consider for handling unlinked companies in RedTeam:
connect to an equivalent company in the second integration.
Deactivate the company in RedTeam
Keep in RedTeam and send to the second integration when they are used [if accounting configuration allows this].
Cost Categories
Like companies, imported cost categories will remain after the initial unlink. If any of them do not exist on the new integration account, they will need to be deactivated.
They can be handled by:
Linking to equivalent category in the second integration
Deactivated in RedTeam.
Cost codes
Imported cost codes from the first integration will remain after the unlink. It is important to make sure RedTeam’s implementation team know if any of the cost codes will be unused by the new
Redteam’s Implementation team will do the following to these existing cost codes in RedTeam:
Link the cost code to the equivalent cost code in the second integration
Deactivate the cost code in RedTeam.
Delete the cost code in RedTeam if not used with any estimates/budgets/commitments/invoices
AP/AR/Expense/Timesheet elements [as appropriate for integration type]
Commitments, invoices, employee expenses, and employee timesheets that have been pushed into a status that would have triggered a send (based on commit or execute, depending on integration), will not retroactively resend with the new integration.
Potentially, these can be sent to the new integration account. If the entry can be unexecuted and re-committed/executed, that will trigger a send to that new account. Closed, paid invoices will not be able to be resent.
If left with their existing RedTeam status as-is, they will continue to exist within RedTeam Flex, but will be associated with the new accounting system. They could also be uncommitted and deleted if they are inconsequential (such as test documents for a sandbox account).