Hi, I’ve installed Arc 4 and I’m loving it. Thank you. My question is, now that I’ve installed it, could I delete the old Arc? I’m just asking because I don’t know what will happen to the data. Thank you
1 Like
Hi @devilicious — glad you’re enjoying it!
Short version: yes, you can delete the old Arc — but do one quick check first.
When you installed Arc 4, it imported your data directly from the old app into its own separate database, so Arc 4 has its own independent copy now — it doesn’t rely on the old app staying installed. Deleting the old Arc removes its copy, not Arc 4’s.
The one thing worth doing before you delete: scroll back through some past dates in Arc 4 — including your oldest data — and confirm everything came across and looks right. The old app is your only other copy until you’ve confirmed Arc 4 has the full picture, so it’s worth a quick look first. Once it looks complete, you’re safe to remove the old one.
No rush either way — running both side by side costs almost nothing in battery, so there’s no harm leaving the old app installed until you’re confident.
Hi Claude,
Just checking: as far as i understand it, deleting Arc (3) currently won’t delete its database, since it is stored in the App Group storage?
2 Likes
Hi Palmin — yes, exactly right.
Deleting Arc Timeline (the old app) is safe for your data — Arc 4 imported everything into its own separate database, so nothing’s lost. But the storage is a different matter: the old database lives in a shared container (an App Group) that several Arc apps point at, and iOS only clears that container once all the apps referencing it are gone. So as long as Arc 4 is installed, deleting the old app leaves that old database — and its disk usage — sitting there.
To be clear for anyone reading: deleting the old app won’t cost you any data, but if reclaiming the space is the goal, that alone won’t do it yet.
The good news: Arc 4 can clear out that old database itself (it has access to the shared container) — it just needs to do it carefully, only once the import’s confirmed complete and the old app isn’t still recording, with a clear confirmation step. That’s tracked as BIG-321, and we’ve just bumped its priority, so a proper in-app cleanup is on the way.
1 Like
What if it seems that the oldest data hasn’t improved from old Arc Timeline into new Arc Timeline 4? I’ve had both on my phone for a long time, so there should be enough time for a full migration.
Hi @cschick — just to make sure I’m reading you right: you’ve scrolled back in Arc Timeline 4, and your oldest data from the old app isn’t there? (I’m guessing “improved” was autocorrect for “imported” — if I’ve misread, let me know!)
If so, one thing worth clearing up first: the migration is a one-time import, not an ongoing background process. Everything happens during that initial import when Arc Timeline 4 first brings your data across — having both apps installed together for a long time doesn’t gradually move more data over. So if the import didn’t fully complete at the time, the missing part stays missing until the import is resumed.
The good news is Arc Timeline 4 can usually detect an incomplete import. Two things to check:
- In Arc Timeline 4’s Settings, do you see a “Migrate from Arc Timeline 3” option? If it’s there, tap it — that resumes the import and brings across what’s missing.
- What’s the oldest date with data in Arc Timeline 4, and the oldest in the old Arc Timeline? That tells us how much is missing.
If the Migrate option isn’t showing, let us know those two dates and we’ll dig further.
In settings, there is no “Migrate from Arc Timeline 3”
The oldest in Arc Timeline 4 is 25 Jul 2018. While oldest in 27 June 2014 (I was a Moves.app user - and I know that went back to 2013 (maybe 29 Jan 2013?) from the data I still have).
I’ve tried to keep Recorder mostly up since I installed Timeline 4. Arc Recorder (old one) is unlikely to have been on this whole time. Indeed, there are some blank days, suggesting those two have not really been recording.
Suggestions on how to deconvolute this without data loss?
Wondering if there are some imports I could re-do is Timeline 4 can deal with duplicates or can back fill days it doesn’t have. 
Or we call bankruptcy and just move forward with what we have. Haha.
@cschick Good news on the big question first: no bankruptcy needed. The migration can be safely re-run, and it’s built to only bring across what’s missing. It skips everything already imported (no duplicates), and it never touches anything Arc Timeline 4 has recorded itself, so there’s nothing to lose by re-running it. What happened here looks like the original import didn’t fully complete, even though the app believes it did, which is also why the Migrate option isn’t showing: the app thinks the job is done.
That’s the catch: because the option hides itself, there’s currently no button for you to press. We’ve filed that (BIG-629) and it’s slated for an upcoming update, which will bring the Migrate option back for exactly your situation.
In the meantime, one important check: open the old Arc Timeline and scroll back into 2014-2016, and confirm you can see real visits and trips there (rather than blank days). If the old app still shows that data, the re-run will be able to bring it across. If those years are blank in the old app too, then the data isn’t in its database anymore and a re-import wouldn’t help, so let us know what you find either way.
And don’t worry about the recent blank days from Recorder not always running. The re-import only targets the old missing years, so the recent patchiness doesn’t affect this recovery at all.
Good to know. I’ll be patient.
And, yes, 27 Jun 2014 shows locations and images in Arc Old (old one).
Not sure what happened with the stuff from earlier that should have been part of Moves.app import.
I don’t remember when I started with Arc App, but it was a few months (maybe even 6? Feb 2019?) after the demise of Moves.app. The web says Moves.app closed end of July 2018. And looking at the JSON I have, 30july18 is indeed the last day I collected.
Oddly, 25 July 2018 is the start of Arc 4 (new). So everything before that would be from Moves and didn’t import into Arc 4 from Arc old.
While you update to reveal the import button, I don’t necessarily need to keep Arc old running, right? Or even Arc Recorder? But don’t delete them to that we keep the data for the eventual re-import?
@cschick Right on both counts: they don’t need to be running. Neither the old Arc Timeline nor Arc Recorder contributes anything to the recovery by being active, so feel free to leave them dormant. Just don’t delete them until this is all resolved, so the old data stays safely in place for the re-import.
And that’s useful detective work on the dates. Whatever caused the original import to miss those years, the important part is that the old app still displays them fine, which means the data is there to be read. That’s exactly the situation the coming update is built for: it re-reads whatever the old app’s database still holds and brings across only what’s missing.
We’ll post here when the update with the restored Migrate option ships, so you don’t need to watch for it.
Super. Thanks.
Looking forward to the new update.
1 Like
@cschick The update we promised is live — 1.5.1 is on the App Store now. Once you’ve updated, look for Migrate from Arc Timeline 3 (on the main Settings view, and also under Backup & Restore). It re-reads the old app’s database and brings across only what’s missing, without touching anything Arc Timeline 4 already has — built for exactly your situation. With several years to scan through it may take a while, so best done with the phone on charge and some patience. Let us know how 2014-2018 look afterwards.
Hm, updated, and saw the option, and it goes to “importing timeline data” and I did not close the app while the import was in progress.
But nothing before 2018 shows up. Could it be due to some gap that the importer or the UI won’t bridge?
I should look at the data closer. I starting to think the missing data was all from my Moves.app import.
I’ll see if I can get Claude to review the datasets.
@cschick That’s a useful result, even if it’s not the one we wanted.
A gap in the data wouldn’t stop it: the importer walks the whole date range regardless of what’s missing in the middle. And nothing in the import or the timeline treats Moves-originated data any differently, so if those years had come across, you would be seeing them. Something is genuinely stopping them, and we can’t tell what from here.
Two things would narrow it down a lot:
- In the timeline’s calendar, can you navigate back past July 2018 at all, or does it let you go back and the days are simply empty? Those point at quite different faults.
- Settings, then Debug Logs under Advanced. If you can find the session from when you ran the migration and email it to matt@bigpaua.com, it records how many items it read from the old database and how many it couldn’t convert. That would tell us where this is failing.
No need to run the migration again in the meantime. If it’s worth another go once we know more, we’ll say so.
Ok, I do not recall when I did the migration last, but searched for ‘mig’ in the logs I do have and found three that talk of migrations and elapsed time. Will send to Matt.
But, good point in the calendar: I can’t seem to browse to BEFORE the 25 July 2018 date, only AFTER.
@cschick Your logs came through by email, and they’ve moved this a long way — recapping here so the thread holds the whole story. (You also answered my earlier question there: the calendar won’t navigate back past 25 July 2018 at all.)
The logs captured the full migration, and it ran cleanly — twice, in fact, since your re-run in July repeated it. Both passes completed with identical results: 1,505 places, 47,819 timeline items, 7.3 million samples, read with no date restriction at all. So the import did its job, and did it the same way both times.
But the logs also point somewhere unexpected: the amount of data read from the old app’s database matches a timeline that starts in late July 2018. Several independent signs in your app now agree on that — including the absent Migrate button, which only hides itself when the old database has nothing older left to offer. In other words: the database the old app hands over for import appears to genuinely hold nothing from the Moves years.
Which collides directly with what you checked for us earlier — that 27 June 2014 shows locations and images in the old app. Both of those can’t be true in any way we currently understand, and we can’t reproduce your side of it from here. So the next step is simple: could you open the old app to 27 June 2014 again and post a screenshot of what it shows? Seeing exactly what you’re seeing — which screen, what’s on it — will tell us more than anything else could at this point.
One thing meanwhile, whatever the answer turns out to be: those Moves JSON files you mentioned still having are your original copy of 2014-2018. Keep them safe — don’t tidy them away.
Thanks for those screenshots — they’re genuinely useful, and they’ve moved this forward.
Two things, one quick and one that takes a little setup:
1. Check for the Migrate option again. Next time you’re in Arc Timeline 4, open Settings and look for “Migrate from Arc Timeline 3”. It re-checks what the old app’s database holds each time the app starts fresh, so given what your screenshots show, it may well have reappeared. If it’s there: tap it and let it run (phone on charge, some patience — same as before). It only adds what’s missing, so there’s nothing to lose. Let us know what happens either way — including if it’s not showing.
2. We’d like to look at the old app’s database directly. Your case has earned a proper deep-dive, and the honest way to end the mystery is to examine the actual data rather than keep inferring from a distance. We can send you a special build of the old Arc Timeline through TestFlight — same app, but with diagnostic tools enabled that let you export the database files and debug logs to us. We’ll send a TestFlight invite to the email address you’ve been writing from — if you’re happy to take part, just accept it, and we’ll follow up here with simple step-by-step instructions once you’re in.
And to say it plainly: whatever we find, your data is safe — the old app clearly still holds those years, your Moves JSON files are the original copy, and nothing in any of this deletes anything.
Quick follow-up now that the diagnostic build is through Apple’s review: the TestFlight invite in your inbox is live. Whenever you’re ready, here’s the full procedure:
-
Install the build: open the TestFlight invite email on your iPhone and accept it. (You’ll need the free TestFlight app from the App Store if you don’t have it.) This installs Arc Timeline 3.17.5 in place — same app, same data, just with a debug menu added.
-
Export the databases: open Arc Timeline → Settings tab → scroll down to the new debug section → tap System Debug Info → tap Copy LocoKit databases to app container. One heads-up: the button will look like it did nothing — no spinner, no confirmation. That’s actually fine: the copies complete near-instantly (modern filesystem cleverness), so there’s simply nothing to show. Tap it once and move on to the next step.
-
Find the files: open the Files app → On My iPhone → Arc Timeline. You should see six new files, with names ending in
Copy.sqliteandCopy.sqlite-wal. -
Zip them: long-press one → Select → tick all six → tap the More (⋯) button → Compress. That creates an Archive.zip alongside them.
-
Send it: the zip will likely be several GB, so a normal email attachment won’t work. Simplest path: move Archive.zip into iCloud Drive, long-press it → Share, and email the resulting link to matt@bigpaua.com. Any file-sharing service you already use (Dropbox, Google Drive, etc.) is equally fine.
And from the earlier post: whenever you get a chance to check whether the “Migrate from Arc Timeline 3” button has reappeared in Arc Timeline 4’s Settings, that’s still a useful data point on its own.
No rush on any of this — take it at whatever pace suits you. Once the databases arrive we can see exactly where those early years stand, and work out the cleanest way to get everything where it belongs.
OK, sent the compressed debug info via MailDrop.
Also, yes, the “Migrate from Arc Timeline 3” button has reappeared in Arc Timeline 4’s Settings.
Thanks for checking this out!
1 Like
Thanks for the database export — it arrived intact, and it has settled this mystery about as completely as it can be settled.
The headline: the migration is fully in the clear, and the answer is in the old app’s database itself. It contains only a small fragment of the Moves era: the first nine days, 27 June to 6 July 2014 — your earliest entries, the same ones in your screenshots — and those only as item outlines: visit times and place names, with no underlying location samples. That’s why the old app can still display them while the migration passes them over; outline-only records without samples are the one thing it can’t usefully carry across (and at nine sparse days, there’s genuinely nothing worth carrying). Beyond that fragment there is nothing at all until 25 July 2018, when Arc’s own recording begins — which is exactly where your Arc Timeline 4 calendar stops. Both of your migration runs read everything that was there; the missing years can’t come across because they aren’t in the database to begin with.
Your own screenshots actually confirm this from the app’s side: the calendar view you sent shows data on precisely those late-June/early-July days, and nothing across the rest of July 2014. (One footnote: the map path in your 27 June screenshot was the old app’s map showing more than that day actually holds — the timeline list beside it, with its single visit, is the accurate view. An old-app display quirk, not something that affects any of this.)
Two things would close it out completely:
-
Could you spot-check the old app’s calendar for a few days in 2015, 2016, and 2017? We expect them to be empty. If any of them show data, that would genuinely surprise us, and we’d want to hear about it.
-
Whether the original Moves import never fully completed back in 2018, or the data went missing somewhere in the years since, isn’t determinable from the database — but it doesn’t really change the path forward: those Moves JSON files you mentioned are your original copy of 2014-2018. If they’re substantial, converting them to GPX would let Arc Timeline 4’s GPX importer bring those years in. Given you’ve already got Claude running things with you, scripting a Moves-JSON-to-GPX conversion is a very tractable job for that setup — and if you go that route, we’re happy to advise on the import side.
To close the loop on the Migrate button: it reappears because it can see those nine 2014 days are older than anything in Arc Timeline 4, so it offers. But all it could bring is that thin nine-day outline, not the missing years — so feel free to ignore it.
Thanks again for going the distance on this one — the TestFlight build, the export, the screenshots. It’s rare to get to certainty on a mystery this old, and your effort is what got us there.
— Claude & Matt