Move records between apps
C
Chris Darden
I was surprised to see this isn't a base feature. You would think there would be instances where people would want to move records entirely into other solutions.
Frank Arnold
Important... I often use this in Coda to move a data set into a kind of archive table. Buttons and automation that would support this would also be ideal for simply moving a data record
Ottawa Admin
This would be ideal when using SmartSuite as an ATS/HRIS. Right now, we use SmartSuite to track job applications that are submitted through a form. However, once they hit the end of the hiring pipeline - either hired or rejected - they just sit at the bottom of my table.
I don't want to lose the application form with all it's filled out fields, because I want to know if this person has applied in the past. I would love to be able to move their application from an "Actively considering" table into an "Archived Applications" or an "Onboarding" table automatically based on conditions.
J
Jay P
I don't understand why this isn't already a feature.
We were coming from ClickUp but will now have to reconsider and perhaps stick with ClickUp due to this not being a feature.
I've wasted a huge amount of time learning SmartSuite with the intention of migrating our business from ClickUp, just to find out it can't do something as simple as move Records from one app to another for a smooth pipeline process?
The whole point of a tool like this is that it increases our productivity, no one has time to manually go in, create new fields and then copy paste huge amounts of Records across. Please add this ASAP.
Can someone let us know if this is coming? Otherwise we'll have to stick to ClickUp.
M
Michelle Laybolt
The ability to move records between apps would drastically improve my team's workflow. As it stands right now, in order to properly follow our process, I've had to write automations to essentially create new records in another app as a client moves through each stage. This involves meticulous mapping of fields to ensure the information is properly input; I've noticed an increased amount of automation failures with this method, and because we are having to create new records each time a client's file changes, there are hundreds of "old" records that are no longer up to date. We have to go back and delete the previous record each time, otherwise we have a bulk amount of unnecessary records causing confusion in the pipeline.
Copy and pasting records has not solved this issue either, as we have hundreds of clients updating their files at any given time; if we were to copy-paste files, crucial information may be missed.
We were previously using ClickUp and enjoyed the ability to move a single task through each process from start to finish. While we moved to SmartSuite for the advantages of better customization and overall improved support, this is a major pain point for our small team.
That being said, there are many features of SmartSuite that we love! Hopefully this feature can be added sometime soon.
A
Anders Hansen
As a large venue and congress business, I would import records from several other platforms and afterwards move records to appropriate apps where fields are the same or very close to same. Obviusly if fields are not a complete match doing move a mapping feature like import have would be great, otherwise discarding fields without a match would still work for me.
Having apps with different terminology for records even though fields are the same, is a nice feature, as moved records hopefully inherit the terminology of the app moved to. Ex: Some of my teams are handling general tasks while others do booth deliveries, same field structure, but different record naming. Same goes for grouping, column ordering and sorting. Each team prioritise same data differently.
My teams are very mobile centric, and some team members are somewhat late to the whole app era :-) simplifying data in clean app views are going to make life a hole lot smoother.
I defiantly upvote this feature.
Pierre Becher
Jon Darbyshire Moving records would be extremely helpful in small business setups when you have multiple apps and the records need to travel through various connected workflows like this:
App 1: Project Sales
App 2: Project Delivery
App 3: Project Billing
I assume one challenge is that fields are specific per app and cannot be reused in another app? So when moving a record from app 1 to app 2, app 2 doesn't know what fields have been available in app 1 and it would either loose all fields or duplicate them, which both isn't a great solution.
Michelle L
Pierre Becher: Agreed. My team goes through a process of client/patient intakes, then processing payments based on their services, prepping the work for said services and finally assembly for delivery to client. There are different aspects that only pertain to each stage, but if we were to migrate them to one app the list of fields would be astronomically long.
Perhaps a prompt to map the data from field to field (similar to how their data import works) when moving a record would help mitigate this issue?
A
Adam Johnston
Seems to me this could only work if the apps have exactly the same fields - and if they have exactly the same fields, isn't it easier just to combine them into one app?
You could show the difference between records that used to be in different apps using a status field, and have everything look exactly the same as when you had different apps by creating different views with filters on that status field
A
Andrew Jones
This would be very helpful for moving a record through a pipeline
Sarah O'Dell
This would be so helpful! When someone on the team puts a task in the wrong app/solution, just be able to move it and not delete and recreate
Oscar Viniegra
Sarah O'Dell: Although if the structure is the same in both apps, you can copy the whole record and paste it in the other one
Load More
→