Data migration route
Sage Timeslips to iManage Cloud migration
Sage Timeslips is a desktop accounting and billing system, and iManage Cloud is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
Sage TimeslipsDesktop- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
iManage CloudCloud- Contacts: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- 3 mapped
- 1 to confirm
- 4 archived
What moves
What moves from Sage Timeslips to iManage Cloud
Each row is a kind of record Sage Timeslips holds, whether iManage Cloud has a place for it, and what is planned. On this route three kinds need mapping, four kinds have no place in iManage Cloud and are archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partBills by client; many firms enter each matter as its own client. | Has a place in partAs a workspace with client and matter metadata. Parties and status stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | Held in partClients and their contacts. | No place | Kept as a readable archive |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes can be loaded as documents on the matter. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expense entries, called slips. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldBills the firm designs itself, payments and receivable balances. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held in partClient funds accounts track money held for clients. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held | Has a place in partA fixed number of custom profile fields, each a validated list. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partBill layouts designed in the product. | Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools. | Carried with mapping |
What the plans mean
- Carried with mapping
- iManage Cloud holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
- Kept as a readable archive
- iManage Cloud has no place for it. It is exported in a format that opens without Sage Timeslips and handed to the firm as a read-only archive.
The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.
This kind of move
Only the documents have a place here.
iManage Cloud is a document management system: it takes files and the details that describe them. Most of what Sage Timeslips holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Sage Timeslips produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in iManage Cloud in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
Sage Timeslips runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. iManage Cloud is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Sage Timeslips
Timeslips does one job, so a move off it is about time, bills and balances, with matters and contacts built from what the billing records imply. The main decision is how the firm used the client list. Some entered one client per matter, others one per person. That convention is read from the data before any mapping is done.
A client may be a matter
The program bills clients, and firms that needed matters adapted the client list to carry them. A common pattern is one Timeslips client per matter, with the two nickname fields holding the client name and the matter. The move turns that into clients with matters beneath, which means deciding which entries are the same person.
Slips are the history
Each piece of time and each expense is a slip with a date, timekeeper, activity, rate and billing status. Unbilled slips become unbilled time and disbursements in the destination. Billed slips are history, loaded where the new system accepts billed entries and otherwise left in a read-only copy with the invoices.
Client funds and trust
Money held for a client is tracked in client funds accounts inside Timeslips. A firm that holds trust money may also keep a formal trust ledger and bank reconciliation in an accounting program. Both are looked at, and the balance loaded as trust is the one that agrees to the bank.
Firebird behind the program
Timeslips Premium stores its data in a Firebird database, either on one PC or on a database server for network installs. On a network the database components sit on the server and the program in a shared folder. A backup made from inside Timeslips gives a copy to work from without disturbing the live database.
The books are in another product
Receivables are kept in Timeslips, but the firm’s general ledger sits in a separate accounting package. The receivable balance in Timeslips and the debtors figure in that package should agree before cutover. Where they have drifted apart, the firm decides which is right before either is loaded.
Where it is going
Arriving in iManage Cloud
Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.
Client and matter lists first
Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.
One workspace per matter
Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.
Authors must be known users
Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.
Hybrid security
iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.
New numbers, original dates
Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Sage Timeslips holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into iManage Cloud and checked against Sage Timeslips: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Sage Timeslips, a final pass over a weekend picks up what changed since the trial. Sage Timeslips is kept read only as the fall-back record.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Sage Timeslips and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Sage Timeslips holds
What is in it, how its records link, and where each piece would sit in iManage Cloud. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
Beyond the data
Setting up iManage Cloud
Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.
Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.
Set-up decisions in iManage Cloud
- Library structure and captions for client, matter and other fields
- Workspace templates, folder names and Flexible Folders rules by practice area
- Document classes, subclasses and the profile fields each one requires
- Roles, groups, default security and walls for restricted matters
- Workspace creation fed from the practice management system’s matter list
- Work Desktop, Outlook email filing and Mobility on each device, with training
Questions
Sage Timeslips to iManage Cloud: what firms ask
Can we split our client list into clients and matters?
Yes, and it is usually the main clean-up task. The analysis groups Timeslips clients that look like the same person or company and proposes a client with matters beneath. Someone at the firm then reviews the list, because only a person who knows the files can say whether two similar names are one client.
Do our bill layouts carry over?
No. Layouts designed in Timeslips belong to it. The firm chooses the formats it still sends, and each is rebuilt as an invoice template in the new system. Clients who receive LEDES files are tested separately with a real invoice before the first live bill run.
What happens to our custom fields?
Custom fields are listed with how often they are filled, and the ones that matter are mapped to fields on the client or matter in the new system. A field that only ever held a matter number or a file reference usually becomes the matter number itself.
Do trust balances in Sage Timeslips have a place in iManage Cloud?
No. iManage Cloud does not keep trust ledgers. Trust records from Sage Timeslips are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records iManage Cloud has no place for?
On this route that is contacts, time entries, billing records and trust ledgers. They are exported from Sage Timeslips in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Sage Timeslips data is loaded into iManage Cloud?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Sage Timeslips and into iManage Cloud
Other destinations from Sage Timeslips
Other systems that move into iManage Cloud
Where to start
Before and after the move.
Choosing the system comes before a migration. Setting it up and putting AI to work come after.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Sage Timeslips and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Sage Timeslips to iManage Cloud?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.